Jira and Linear
OpenSCRUM can connect to Jira and Linear so that you can import issues into a planning poker session as stories, instead of typing them in.
OpenSCRUM only reads from your tracker. It never creates, changes or comments on issues, and agreed estimates are not sent back yet.
Connecting a tracker
An organisation has one connection to Jira and one to Linear. An owner or admin sets each up once, in Settings under Issue trackers, and everyone in the organisation can then import through it.
Other members only see a tracker in Settings once it is connected. Until then there is nothing there for them to do, so it is not shown.
Everyone shares the connection's access
Anyone in your OpenSCRUM organisation can import any issue that the connected account can see. Connect an account whose access matches what your team should see. If your tracker lets you limit what a token can do, read-only access is all OpenSCRUM needs.
Jira
OpenSCRUM supports Jira Cloud — sites whose address ends in atlassian.net. Jira Data Center (Jira on your own servers) is not supported yet.
- Create an API token in your Atlassian account settings.
- In OpenSCRUM, go to Settings and, in the Jira box under Issue trackers, enter:
- Jira address — for example
yourcompany.atlassian.net. You can paste any address from your Jira site. - Your Jira email address — the email of the Atlassian account that created the token.
- API token — the token from step 1.
- Jira address — for example
- Choose Connect Jira.
Linear
- Create a personal API key in Linear's settings, under Security & access.
- In OpenSCRUM, go to Settings and, in the Linear box under Issue trackers, paste it into API key and choose Connect Linear.
What happens when you connect
OpenSCRUM checks the details with the tracker straight away. If the tracker does not accept them you see a message and nothing is saved.
Once connected, the box is marked Connected and shows what it is connected to: your Jira site's address, or your Linear workspace's name.
The token is encrypted before it is stored in OpenSCRUM's database, and it is never shown again or sent to anyone's browser.
Disconnecting or replacing a connection
An owner or admin can choose Disconnect in a tracker's box and confirm. Stories that were already imported stay in their sessions, with their links.
To use a different account or token, disconnect and connect again.
If a tracker stops accepting the saved token — for example because the token was revoked or has expired — importing shows a message asking for the tracker to be connected again.
Importing stories
In a planning poker session, under Stories, choose Import from Jira or Import from Linear. Only connected trackers are offered.
- Choose the Jira project or Linear team to import from.
- Tick the issues you want. To find a particular issue, type part of its title into Search titles. Issues you have already ticked stay ticked while you search.
- Choose Import.
Each imported issue becomes a story, in the order shown in the list. The story shows the issue's key (such as WEB-12), which links to the issue in your tracker.
Things to know:
- Which issues are listed: up to 50 unfinished issues, most recently updated first. In Jira, unfinished means any status that is not in the "Done" category; in Linear, anything that is not completed, cancelled or a duplicate. Use the search to find issues beyond the first 50.
- Which projects and teams are listed: the first 100 that the connected account can see.
- Importing twice: an issue that is already in the session is skipped, so it is safe to import overlapping selections.
- No syncing: the title is copied when you import. Later changes to the issue in your tracker do not update the story.
Requirements for self-hosting
The OpenSCRUM server contacts the trackers directly, so it needs outbound HTTPS access to your Jira site (*.atlassian.net) and to api.linear.app.
Stored tokens are encrypted with a key derived from AUTH_SECRET. If you change AUTH_SECRET, the stored tokens can no longer be read and each tracker must be connected again.
Not available yet
- Sending agreed estimates back to Jira or Linear.
- Jira Data Center.
- Signing in to a tracker with a "Connect" button (OAuth) instead of pasting a token.
- A personal connection for each person, so that imports follow their own access.
- Trackers other than Jira and Linear.