Manage projects with GitHub

Your team uses a GitHub Project to plan an upcoming release. During a brainstorming session, you added several quick draft items directly on the project board so you wouldn't lose the ideas. One of those draft items, 'Add dark mode toggle,' has now been fully scoped and needs to be assigned to a developer, tracked in a specific repository, and referenced from a pull request. What should you do with the draft item?

A product team uses a GitHub Project (the new Projects experience) to track work across multiple repositories. The project manager wants to see all items visually organized into columns representing 'To Do', 'In Progress', and 'Done', and wants to drag items between these columns to update their state. Which combination should the project manager configure to achieve this?

A product team is planning their v2.0 release, which bundles about 30 issues and pull requests that must all be completed by a fixed launch date. They want a single place to see how many of these items are done versus still open, along with the shared due date. Which GitHub feature should they use to group these items and track progress toward the release deadline?

A product team wants to visualize their work as cards that move through columns representing stages like 'To Do', 'In Progress', and 'Done'. They want a Kanban-style view where team members can drag items between stages to reflect their current status. Which GitHub Projects layout should they choose?

Your team uses a GitHub Project to plan a product launch. The project manager wants to visualize when each initiative starts and ends across the next quarter, showing durations and how work items overlap over time. Which project layout should the team switch to?

Your team uses a GitHub Project to manage a backlog of 80 issues. During sprint planning, the product manager wants to see all items in rows and quickly edit each item's Priority and Iteration custom fields side by side, similar to working in a spreadsheet. Which project layout should the team switch to for this task?

A product manager is reviewing a GitHub Project (Projects) board that contains dozens of issues spanning several teams. She wants the board layout to visually separate the cards into horizontal swimlanes so that all items belonging to each team appear grouped together, making cross-team workload easier to scan. Which project configuration should she use to achieve this?

A team lead wants a visual chart in their GitHub Project that shows how many items currently fall into each Status value (Todo, In Progress, Done) so they can quickly spot bottlenecks during weekly standups. Which GitHub Projects capability should they use to create this view?

A product manager runs a GitHub Project (the new Projects experience) to track a team's sprint work. She wants to see charts showing how many items were completed over the past several weeks and how work is distributed across statuses, so she can report on the team's progress and velocity to leadership. Which GitHub Projects feature should she use?

A product team stores dozens of issues in a repository. Some are defects, some are feature requests, and some are documentation tasks. The team lead wants an easy way to categorize each issue so anyone can quickly filter the issue list to see only defects. Which GitHub feature is designed for this categorization and filtering?

Your team uses a GitHub Project to track work. During triage meetings, teammates want a consistent way to mark each item as 'High', 'Medium', or 'Low' priority so the values can be filtered and grouped reliably, and so people cannot type free-form text. Which project configuration should you set up?

Your team creates a new GitHub Project to track work for the 'web-app' repository. The project lead wants every newly opened issue in that repository to automatically appear on the project board without anyone manually adding it each time. Which built-in project feature should you configure to accomplish this?

A product team uses a GitHub Project (Projects experience) to track their backlog. They want items to automatically move to the 'Done' status column whenever the linked issue or pull request is closed, without a team member having to update the status field manually. Which built-in Projects feature should they configure to achieve this?

A maintainer of a popular open-source repository spends significant time each week typing nearly identical responses to issues that lack reproduction steps, asking reporters to provide a minimal example and environment details. They want a faster way to insert this standard message when commenting, while still being able to edit it before posting. Which GitHub feature best addresses this need?