I’m a bit confused about GitHub projects. I’m part of an org and I’m leading a project. I made a project in the org and someone else set up a repository. However, that repository also has its own Projects tab. What is the intended use of both setups? Should I plan everything in the org project and overlook the repository one, or is there a way to use them together? I’m trying to figure out the best method to organize my work. Thanks for any insights!
I’ve been in a similar situation, and here’s what I learned through experience:
Organization Projects are better for high-level planning across multiple repositories. They’re great for managing work that spans different codebases or teams within your org.
Repository Projects, on the other hand, are more focused. They’re ideal for tracking issues, pull requests, and tasks specific to that particular repository.
In your case, I’d recommend using the Organization Project for overall planning and coordination. Use it to set milestones, track major features, and manage resources across teams.
Then, utilize the Repository Project for day-to-day development tasks, bug tracking, and code-specific items. This way, developers can easily manage their immediate work while you maintain a broader view of the project.
The key is to link items between the two. When creating tasks in the Org Project, reference the relevant Repository issues. This creates a clear hierarchy and helps everyone understand how their work fits into the bigger picture.
Remember, it’s not about using one or the other exclusively, but leveraging both to create a comprehensive project management system.