Skip to main content

Managing projects (classic)

Learn how to create and manage classic projects

Notes:

  • Projects, the all-new projects experience, is now available. For more information about Projects, see "About Projects" and for information about migrating your classic project, see "Migrating from Projects (classic)."
  • You can only create a new classic project board for an organization, user, or repository that already has at least one classic project board. If you're unable to create a classic project board, create a project board instead.
  • About projects (classic)

    Projects (classic) on GitHub Enterprise Cloud help you organize and prioritize your work. You can create classic projects 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.

  • Creating a project (classic)

    Classic projects can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.

  • Editing a project (classic)

    You can edit the title and description of an existing classic project.

  • Linking a repository to a project (classic)

    You can link a repository to your organization's or personal account's classic project.

  • About automation for projects (classic)

    You can configure automatic workflows to keep the status of classic project cards in sync with the associated issues and pull requests.

  • Configuring automation for projects (classic)

    You can set up automatic workflows to move issues and pull requests to a classic project column when a specified event occurs.

  • Copying a project (classic)

    You can copy a classic project to quickly create a new project. Copying frequently used or highly customized classic projects helps standardize your workflow.

  • Changing project (classic) visibility

    As an organization owner or classic project admin, you can make a classic project public or private.

  • Closing a project (classic)

    If you've completed all the tasks in a classic project or no longer need to use a classic project, you can close the classic project.

  • Reopening a closed project (classic)

    You can reopen a closed classic project and restart any workflow automation that was configured for the classic project.

  • Deleting a project (classic)

    You can delete an existing classic project if you no longer need access to its contents.