Connect a Projects board, map fields and create work.
Reviewed · 2026-10-12
On this page · 3
1. Create and identify the board
GitHub organization → Projects → New project → Table or Board → name → Create project. For an existing board, click its name in Projects.
Copy the opened board URL https://github.com/orgs/ORG/projects/NUMBER. A repository /projects URL is only a directory, not a board.
In LUNA open Research work → Linked boards → Add GitHub Projects. GitHub / Projects board is preselected. Enter a name and board URL; Repository to collect uses OWNER/REPOSITORY. Each grant or project uses one board. Edit or disable the previous connection before replacing it.
2. Board and repository permissions
GitHub avatar → Settings → Developer settings → Personal access tokens. For an organization fine-grained token, select its repository, grant Contents read and Issues read/write if creating or changing issues. Under Organization permissions grant Projects read or read/write for changes. Complete organization approval when required.
If fine-grained tokens are unsupported for your account/board operation, follow the official Projects API instructions: classic read:project for reads or project for writes, plus repo for private repositories. Authorize Configure SSO when required by the organization.
Paste the token into the connection token field. Explicit create/edit actions also use this token, so writing requires the corresponding write permissions.
3. Map fields and create work
Save → Collect now → Research work → Linked boards. Open Field mapping and map Status, Due date and Priority to their corresponding platform roles. This changes display/aggregation interpretation only.
To add a missing date field on GitHub: Table → + at the right → New field → Due date → Field type Date → Save. Collect again in LUNA to refresh the field choices.
Create work → title and body → Status such as Todo/In progress → due date, priority and assignees → confirm GitHub write → Save. LUNA creates an Issue, adds it to the board and applies fields. Assignees need a profile GitHub ID and must be assignable on GitHub.
If the result needs review, open the created GitHub issue before retrying. Uncertain create operations are not retried automatically.