GitHub Projects
One list of work, seen as a table, a board or a roadmap
The same items as a table, a board or a roadmap.
A GitHub project is a list of issues and pull requests that you can look at in different ways. As a table, it is a spreadsheet: one row per item, easy to sort and edit. As a board, the same items become cards in columns, one column per status. You drag a card to move it along. And as a roadmap, the same items sit on a timeline, so you can see what happens when. Three layouts, one set of items.
GitHub Projects · Going deeper
About Projects
Items from many repositories, owned by a person or organization.
Fields
The project adds its own fields to every item
The issue brings labels and assignees. The project adds custom fields.
What can a project know about each item? An issue already carries some information from its repository: who is assigned, its labels, its milestone. The project adds fields of its own. Status and priority are single select fields, with a list of options. A sprint is an iteration field. An estimate is a number, and a target date is a date. Once the fields exist, you can sort, group and filter every view by them.
Fields · Going deeper
Field types
Text, number, date, single select, iteration.
Check yourself
Which layout is this view using?
Workflows
Built-in workflows update the project for you
Built-in workflows set Status when items are added, closed or merged.
Nobody enjoys keeping a tracker up to date by hand, so a project can do it for you. When an item is added, a workflow can set its status to to do. When an issue is closed, its status becomes done. The same happens when a pull request is merged. Those two are switched on by default. And the auto add workflow watches a repository: any new issue that matches your filter, such as the label bug, joins the project by itself.
Workflows · Going deeper
Ways to automate a project
Auto-add, auto-archive, Actions and the API.
Labels, assignees, milestones
What kind, who, and by when
Labels categorize, assignees own, a milestone tracks progress to a date.
Three simpler tools organize issues and pull requests, with or without a project. Labels say what kind of work it is: a bug, documentation, a good first issue. Assignees say who is responsible. One issue can have up to ten. And a milestone says by when. It groups issues toward a goal, such as version two, with a due date. Here, six of its eight issues are closed, so it shows seventy five percent complete.
Labels, assignees, milestones · Going deeper
More ways to organize
Issue types, sub-issues, saved replies and templates.
Check yourself
Which feature shows this?
Insights
Charts drawn from the project itself
Current charts count items now. Historical charts show change over time.
How is the project going? Insights answers with charts built from the items themselves. A current chart counts items as they stand today. Here, six to do, four in progress, ten done. You choose what to count by: status, assignee, label, or any field. A historical chart shows change over time. The default is called burn up. The dashed line is all the work, and the green line is the completed work. When the gap closes, you are finishing.
Insights · Going deeper
Clue words for managing projects
Board, workflow, insights, milestone and saved reply.
Check yourself
Which feature did this?
Lesson complete
You finished “Managing projects”
Answer the questions along the way to see your score here.