Skip to content
Pealboard

Create and edit an issue

Create

Section titled “Create”
  1. Select New issue.
  2. The Repository is pre-filled with the workspace’s default repository (see Workspaces), when it has one; select Choose a different repository to pick another, or to choose one for the first time if there is no default. This cannot be changed after the issue exists — GitHub has no way to move an issue between repositories through its API. To move work into another repository after the fact, split the issue into sub-issues there instead.
  3. Fill in the title and the body.
  4. Optionally set labels, assignees, a milestone, a project and its field values.
  5. Select Create issue.

The issue is created in GitHub first. Only when GitHub returns it does it appear in Pealboard. If GitHub refuses — a missing permission, a repository the installation does not cover, a label that no longer exists — you see GitHub’s refusal and nothing was created.

Who the author is

Section titled “Who the author is”

Today, every issue is authored as pealboard[bot] with a line naming you, whether or not you have linked your GitHub account in Account → Linked GitHub. Linking is required before an organization can be connected to a workspace; writing issues and comments as you, rather than as the app, is not available yet.

Edit

Section titled “Edit”

Open an issue and edit the title or body in place. Labels, assignees, milestone and project fields are in the Fields panel on the right. Every change is a write to GitHub, applied as soon as you leave the control.

Editing shows the same optimistic behavior as the board: the value changes immediately and moves back with GitHub’s refusal if GitHub does not accept it.

Closing and reopening

Section titled “Closing and reopening”

Close an issue as Completed or as Not planned, which are GitHub’s own two reasons. Both are shown to portal customers as a status word: Completed maps to Completed and Not planned maps to Closed. Reopening sets the status back to whatever the rules derive.

What you cannot do here

Section titled “What you cannot do here”
  • Move an issue to another repository. Split it into sub-issues in the repository the work belongs in instead.
  • Delete an issue. GitHub’s API cannot delete issues; close it instead.
  • Edit a comment somebody else wrote.
  • Convert an issue to a discussion or a pull request.