Projects and fields
Projects lists the GitHub Projects belonging to the connected organization or account, with their fields and the issues in them.
Pealboard does not have a project type of its own. A project is a GitHub Project; a field is a GitHub project field. Pealboard reads them, uses them as dimensions to filter, sort and group by, and writes a value back when you change one.
Field types Pealboard uses
Section titled “Field types Pealboard uses”| GitHub field type | Read | Set from Pealboard | Filter, sort, group |
|---|---|---|---|
Single select, including Status |
Yes | Yes | Yes |
| Number | Yes | Yes | Yes |
| Date | Yes | Yes | Yes |
| Iteration | Yes | Yes | Yes |
| Text | Yes | Yes | Filter only |
| Title, Assignees, Labels, Milestone, Repository | Yes | On the issue itself | Yes |
Status is a field, not a state
Section titled “Status is a field, not a state”GitHub issues have two states: open and closed, and closed carries a reason,
Completed or Not planned. Status is something else: a single-select field on a
project, whose options the project owner writes — Triage, In progress, Blocked,
Done, or whatever the team decided.
Pealboard uses both, and never confuses them. A board grouped by Status moves
a project field. A board grouped by state moves nothing; state changes when you
close or reopen the issue.
Adding an issue to a project
Section titled “Adding an issue to a project”Open the issue and choose a project in the Fields panel. The issue becomes an item in that project, exactly as it would if you had added it in GitHub. Initial field values can be set at the same time.
A request type can add every issue it creates to a project and set field values on creation, so a new request arrives already in Triage.
The items list
Section titled “The items list”Projects → a project lists its items, most recently changed first, with each field value editable in place. Add issue searches every connected repository and adds one; Remove from project removes the card and leaves the issue alone — it stays in its repository, keeps its labels and its comments, and can be added again.
Pealboard stores no ordering for project items. GitHub’s own board keeps one, and maintaining a second copy of it under out-of-order webhook deliveries would be a cost paid for a value only that board reads. So the list is ordered by what changed most recently, and the only move Pealboard offers is Move to the top, whose result is read on GitHub.
What Pealboard never does to a project
Section titled “What Pealboard never does to a project”- It does not create projects.
- It does not create, rename or delete fields, or add options to a single-select field.
- It does not create or edit a project’s built-in automations. GitHub exposes no way to author those through its API; the four built-in rules a project already has continue to run and Pealboard does not interfere with them.
- It does not read a project’s Insights charts. GitHub has no API for them.
If you need a new field or a new option, add it in GitHub. Pealboard sees it on the next sync.