This version of GitHub Enterprise Server was discontinued on 2024-09-25. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise Server. For help with the upgrade, contact GitHub Enterprise support.
Learn how to create and manage projects (classic)
Note
Projects (classic) on GitHub Enterprise Server help you organize and prioritize your work. You can create projects (classic) for specific feature work, comprehensive roadmaps, or even release checklists. With projects (classic), you have the flexibility to create customized workflows that suit your needs.
Projects (classic) can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.
You can edit the title and description of an existing project (classic).
You can link a repository to your organization's or personal account's project (classic).
You can configure automatic workflows to keep the status of project (classic) cards in sync with the associated issues and pull requests.
You can set up automatic workflows to move issues and pull requests to a project (classic) column when a specified event occurs.
As an organization owner or project (classic) admin, you can make a project (classic) public or private.
If you've completed all the tasks in a project (classic) or no longer need to use a project (classic), you can close the project (classic).
You can reopen a closed project (classic) and restart any workflow automation that was configured for the project (classic).
You can delete an existing project (classic) if you no longer need access to its contents.