A project's fields live on the project, not on the issues. Besides built-in ones such as Assignees, Labels, Milestone, Parent issue and Sub-issue progress, you can add custom text, number, date, single-select and iteration (repeating sprint) fields, up to 50 fields in all. For BookNest's board (not run here, see Project Boards):
gh project field-create 1 --owner binarybehemoth --name Priority \
--data-type SINGLE_SELECT --single-select-options "High,Medium,Low"
gh project field-create 1 --owner binarybehemoth --name Estimate --data-type NUMBERViews are saved ways of looking at the same items, each with its own filter (such as is:open milestone:1.2.0), sort, grouping and columns: a table grouped by Priority for triage, a board sliced by area: label, a roadmap laid out on the iteration field. Automation comes in three levels. The Workflows menu has built-in toggles, two on by default that set Status to Done when an item is closed or a pull request merged, plus Auto-add to project (new issues matching a filter such as label:bug) and Auto-archive items. A GitHub Actions 29 workflow can go further through the GraphQL API, for example with actions/add-to-project (https://github.com/actions/add-to-project 716 ) and a project-scoped token stored as a secret (Secrets and Environments). The Insights tab charts fields over time, such as a burn-up of the milestone.