Task 5.1: Project Tracking and organization

• AA board view grouped by Status

  Incorrect

  A board shows items in columns; it doesn't give them dates on a timeline.

• BA label named roadmap on each issue

  Incorrect

  Labels categorize items but don't place them in time.

• CMore values in the Status field, one for each month of the release plan

  Incorrect

  Status values name stages of work; they aren't dates that position items on a timeline.

• DDate fields or an iteration field, with values set on each item

  Correct

  Roadmaps use the project's date and iteration fields to position items on the timeline.

The roadmap layout gives a high-level visualization of a project over a configurable timespan. Roadmaps use your custom date and iteration fields to position issues, pull requests and draft issues on a timeline, and you can drag items to change their start and target dates or iteration. The table layout is a spreadsheet of items, and the board layout spreads them across columns.

• AIt needs a GitHub Actions workflow, because projects have no automation of their own

  Incorrect

  Projects include built-in workflows; Actions is for more control.

• BIt needs a ruleset on the repository's default branch

  Incorrect

  Rulesets govern branches, not project fields.

• CA built-in project workflow already does this and is enabled by default

  Correct

  When a project initializes, the workflows that set closed issues and merged pull requests to Done are on.

• DIt needs an auto-add workflow with a filter on closed issues

  Incorrect

  Auto-add puts items into the project; it doesn't change their status.

Projects include built-in workflows that update the Status of items based on events, such as setting Todo when an item is added or Done when an issue is closed. When a project initializes, two workflows are enabled by default: closed issues and pull requests are set to Done, and merged pull requests are set to Done. For more control you can use the GraphQL API and GitHub Actions.

• AAn issue template in each repository with the request text

  Incorrect

  Templates shape new issues; they don't post her replies.

• BA saved reply in her account, edited as needed before posting

  Correct

  Saved replies are reusable responses tied to her account and work across repositories and organizations.

• CA label named needs-repro

  Incorrect

  A label marks the issue but doesn't write the comment.

• DA pinned issue explaining the rule

  Incorrect

  A pinned issue doesn't add her reply to each issue.

Saved replies let you create reusable responses to issues and pull requests; they can also be used in discussions. They are tied to your personal account, so you can use them across repositories and organizations, up to a maximum of 100. When commenting, you choose a saved reply and can edit its content before posting.

• ANothing; project grouping is only a display setting

  Incorrect

  Dragging between assignee groups changes the assignment.

• BIt adds Ben in the project, but the issue page still shows only Ana as its assignee

  Incorrect

  The issue reflects the change made in the project.

• CIt reassigns the issue to Ben, since project changes sync to the issue

  Correct

  The integration works both ways, so changes in the project show on the issue.

• DIt transfers the issue to Ben's personal repository

  Incorrect

  Assignment doesn't move issues between repositories.

Projects are built from the issues and pull requests you add, and information syncs automatically both ways: when you change information about an issue in your project, the issue reflects it. For example, you can group by assignee and change assignments by dragging issues into different groups.

• AA special repository that stores only a team's documentation and planning notes

  Incorrect

  Projects track work items, not files.

• BA copy of a repository for experiments

  Incorrect

  Projects don't copy repositories.

• CA chat room for a team

  Incorrect

  Projects plan and track work.

• DA table, board and roadmap of issues and pull requests for planning work

  Correct

  That is how GitHub describes Projects.

A project is an adaptable table, board and roadmap that integrates with your issues and pull requests to help you plan and track work at the user or organization level.

• ANo: a project has a single layout that every view must share

  Incorrect

  Each view has its own layout.

• BOnly if the project is public

  Incorrect

  Visibility doesn't affect layouts.

• CYes: each view can be a table, a board or a roadmap

  Correct

  You can set each view to a different layout.

• DOnly in projects owned by personal accounts

  Incorrect

  Organization projects can do the same.

You can view a project as a high-density table, a kanban board or a timeline-style roadmap, and you can set each view in the project to a different layout.

• AApprove, to approve pull requests

  Incorrect

  Approvals are review decisions, not saved replies.

• BMerge now, to merge a pull request

  Incorrect

  Saved replies insert text; they don't merge.

• CTransfer, to move an issue to another repository

  Incorrect

  Transfers are a separate action.

• DDuplicate issue, to mark an issue as a duplicate

  Correct

  GitHub provides a Duplicate issue saved reply.

Besides the saved replies you create, GitHub provides a Duplicate issue saved reply that marks an issue as a duplicate and tracks it with a similar issue.

• ANo: a project belongs to a single repository and only shows that repository's work

  Incorrect

  Projects are created at the user or organization level.

• BYes: one project can hold issues and pull requests from many repositories

  Correct

  Projects can include issues and pull requests from many repositories.

• COnly pull requests, not issues

  Incorrect

  Both can be added.

• DOnly if every repository belongs to the project's own organization

  Incorrect

  Projects can include issues and pull requests from any organization.

Projects are created at the user or organization level. You can add issues and pull requests from different repositories, and even from any organization.