Connect Jira

Connecting Jira lets the team’s thinking, or one group’s, learn from the issues and comments in the Jira Cloud projects you choose, including how work turned out. Only a team’s owners and admins can set it up, and only in a team workspace.

Set it up

1. In Cranes, open Settings › Sources and choose Connect Jira.
2. Fill in:
   • Jira address: like yourteam.atlassian.net.
   • Projects: each project’s key, separated by commas. It’s the prefix on its issue numbers, like OPS in OPS-12.
   • What it feeds: the team’s thinking, or a group you’re in.
3. Choose Continue to Jira, and approve read access in Atlassian. Your account needs to be able to see those projects.
4. Atlassian sends you back to Settings › Sources.

Cranes reads the last 30 days of issues straight away, then changes about every 15 minutes.

What becomes an entry

• Each issue becomes one entry: its key, summary, status, and description. When it changes, including when it’s reopened, done, or abandoned, the newer version replaces the older one, so the thinking learns how work turned out.
• Each comment becomes its own entry, credited to its author’s Jira name.

When someone’s Atlassian account is closed, Cranes removes their name from these entries, as Atlassian requires, and they’re shown as a former Jira user. The words of their issues and comments stay.

Issues are learned in the next pass, not one at a time, and a single issue never becomes the team’s position on its own. Everyone who can read the thinking it feeds can see these entries, so connect a group only when its members may see those projects.

Disconnect

Only owners and admins see Revoke. It stops reading, and removes Jira authors’ names from the entries it brought in. Entries already brought in stay, with their usual entry settings.