Jira

Link an app to a Jira Cloud project, and its tickets in Slack or Microsoft Teams stay in step with the issues in Jira. This page is for the builder who sets up the link. For the click-by-click setup, see the Jira quickstart. Jira support on Microsoft Teams is in beta.

What syncs

The link works both ways, and it joins one app to one project. A ticket opened in the channel creates an issue in the linked project. An issue created in the project creates a ticket. If a project is already linked to another channel, Conclude does not offer it again.

Five issue fields stay in step with the ticket:

Priority only syncs when the project’s issues have a priority field. Without it, the app has no severity attribute. Status is matched by category, not by name.

Comments sync both ways, with their attachments. Tick Sync pinned comments only to change that. Then only pinned messages go from the channel to Jira, while all Jira comments still reach the channel.

Linking a project also changes the app’s attributes. Conclude adds or updates an issue type attribute and an issue status attribute, and it reads their options from the project. If the project has priorities, it also adds or updates a severity attribute. It adds a tag attribute that shows the issue key as a link. Check the Attributes tab afterwards.

Set up the link

1. Add the Jira instance to the organization. In the Admin console, open Apps > Integrations and add Jira by its subdomain. Atlassian asks you to authorize Conclude. You need permission in Jira to install integrations.
2. Link the app to a project. Open the app’s Integrations tab and tick Connect this app to a Jira project. Choose the instance if there is more than one, and pick the project. Set the comment option and the integration account email. Then save.

If the tab says that no Jira integration is available, nobody has done step 1 yet. The app YAML holds the project link under the jira: key, but not the account email. See the Jira connector.

To check the link, open a ticket with /c new and confirm that the issue appears in the project.

Status mapping

Jira workflows differ from project to project. Conclude therefore maps against Jira’s status category rather than the status name. To Do and In Progress keep a ticket open. Any status in the Done category concludes it.

In the other direction, opening or reopening a ticket looks for a To Do status, and falls back to In Progress. Concluding a ticket looks for a Done status. The tables are in the status reference.

Integration account

Conclude posts to Jira as the person who acts in the channel. When that person has not signed in to Jira through Conclude, the integration account posts instead, so set one up. Create the user in Atlassian and choose an account that is not tied to a person, for example “Team user”.

Enter its email in the Email of the Jira integration account field on the Integrations tab. Conclude stores the address on the Jira instance, not on the app, so every app linked to that instance shares it.

Conclude needs a Jira sign-in for the account. Run /c jira login in the app’s channel and complete the Atlassian sign-in as that account.

Commands

The /c jira commands manage the link from the channel:

• status shows your sign-in state, and connections lists the active connections
• login and logout manage your own sign-in
• sync, export and import <issue-id> move one ticket or issue by hand

See Jira commands.

Zendesk is the other two-way integration. See Zendesk.