Skip to main content

Adding notes to a project (classic)

You can add notes to a classic project to serve as task reminders or to add information related to the classic project.


  • 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.


  • You can format your note using Markdown syntax. For example, you can use headings, links, task lists, or emoji. For more information, see "Basic writing and formatting syntax."
  • You can drag and drop or use keyboard shortcuts to reorder notes and move them between columns. For more information about keyboard shortcuts, see "Project boards" in "Keyboard shortcuts."
  • Your classic project must have at least one column before you can add notes. For more information, see "Creating a project board."

When you add a URL for an issue, pull request, or another classic project to a note, you'll see a preview in a summary card below your text.

Project board cards showing a preview of an issue and another project board

Adding notes to a classic project

  1. Navigate to the classic project where you want to add notes.

  2. In the column you want to add a note to, click . Plus icon in the column header

  3. Type your note, then click Add. Field for typing a note and Add card button

    Tip: You can reference an issue or pull request in your note by typing its URL in the card.

Converting a note to an issue

If you've created a note and find that it isn't sufficient for your needs, you can convert it to an issue.

When you convert a note to an issue, the issue is automatically created using the content from the note. The first line of the note will be the issue title and any additional content from the note will be added to the issue description.

Tip: You can add content in the body of your note to @mention someone, link to another issue or pull request, and add emoji. These GitHub Flavored Markdown features aren't supported within classic project notes, but once your note is converted to an issue, they'll appear correctly. For more information on using these features, see "About writing and formatting on GitHub."

  1. Navigate to the note that you want to convert to an issue.
  2. In the upper-right corner of the notes, click . Horizontal kebab icon in upper-right corner of note
  3. Click Convert to issue. Convert to issue button
  4. If the card is on an organization-wide classic project, in the drop-down menu, choose the repository you want to add the issue to. Drop-down menu listing repositories where you can create the issue
  5. Optionally, edit the pre-filled issue title, and type an issue body. Fields for issue title and body
  6. Click Convert to issue.
  7. The note is automatically converted to an issue. In the classic project, the new issue card will be in the same location as the previous note.

Editing and removing a note

  1. Navigate to the note that you want to edit or remove.
  2. In the upper-right corner of the notes, click . Horizontal kebab icon in upper-right corner of note
  3. To edit the contents of the note, click Edit note. Edit note button
  4. To delete the contents of the notes, click Delete note. Delete note button

Further reading