What you need
- A GitHub personal access token with read access to the repositories you want to import from. Create a personal access token ↗ in the connection form takes you to GitHub.
- For GitHub Enterprise: the API URL of your server. For github.com the default
https://api.github.comis right.
The token is stored on your computer, protected by your operating system's secure storage. Sightdeck only reads from GitHub — it does not change issues there.
Connect GitHub
- Open Settings → Integrations and scroll to GitHub.
- Click + Add GitHub connection. Give it a Label (for example your company name), check the API URL and paste the Access Token.
- Under Label to type, decide which GitHub label becomes which task Type. Out of the box
bugbecomes Bug, andenhancementandfeaturebecome Feature. Add more with + Add label. The first matching label decides the type; an issue with no matching label becomes Unclassified and is typed by refinement. - Click Test, then Save.
Add one connection per GitHub account or Enterprise server. If the test fails, the message says why: an invalid or expired token, a missing scope or rate limit, a wrong API URL, or a server error.
Import issues
- Open the project the tasks should go into and click Import from GitHub in the quick-add bar. The button only appears inside a project, once a connection with a token exists.
- With several connections, pick one. Then choose the Repository — type to search the list.
- Narrow the list:
- Filter by assignee starts on
me. Type a GitHub username to see that person's issues, or clear the field to import every assignee. - Filter by label keeps the issues that carry any of the selected labels. No label selected imports every issue.
- Filter by number or title… searches the list.
- Filter by assignee starts on
- Tick the issues you want, or use Select all. Issues already in the project are marked as imported. The open button on a row shows the issue on GitHub.
- Click Import. The summary tells you how many tasks were created and how many were updated.
Only open issues are listed, and pull requests are left out.
What a task gets
- Title — the issue title.
- Summary — the first paragraph of the issue text, shortened to one line.
- Type — from the label mapping of the connection.
- Tags — the issue's labels that already exist as tags in the project, in the project's spelling. Other labels are not added as tags.
- End date — the due date of the issue's milestone, if it has one.
- Link — the issue as the task's external reference, in the form
owner/repo#123, with its URL.
New tasks go through refinement right away, with the issue title and text as input — that is where their estimate and Story Points come from. An issue that was imported before is matched by that reference and refreshed; the Type and tags you set by hand on the task stay as they are.
Related
Working with Jira instead? The Jira import wizard works the same way. Types of your own are set up in Task Types.