Project boards on GitHub Enterprise help you organize and prioritize your work. You can create project boards for specific feature work, comprehensive roadmaps, or even release checklists. With project boards, you have the flexibility to create customized workflows that suit your needs.
Project boards are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can drag and drop to reorder cards within a column, move cards from column to column, and change the order of columns.
Project board cards contain relevant metadata for issues and pull requests, like labels, assignees, the status, and who opened it. To see more details about the issue or pull request, you can easily navigate to it by clicking the link within the card.
You can create notes within columns to serve as task reminders or to add information related to the project board. If the note isn't sufficient for your needs, you can convert it to an issue. For more information on converting project board notes to issues, see "Adding notes to a project board."
There are two types of project boards:
- Repository project boards are scoped to issues, pull requests, and notes within a single repository.
- Organization-wide project boards can contain issues and pull requests from any repository that belongs to an organization.
Creating and viewing project boards
Anyone with read access to a repository can view the repository's project boards. To create a project board, you must have write access to the repository.
Only organization members can view and create organization-wide project boards. If an organization-wide project board includes issues or pull requests from a repository that you don't have permission to view, the card will be redacted.
