To see how to set up the Jira integration for this use case, visit How To Set Up Jira for PM Sync Integration.
Summary
Thoropass offers the ability to send action items to a Jira Cloud project you specify; those action items will be created as tickets in that project. The status and attachments of the action item(s) and ticket(s) will sync between Thoropass and Jira, so you will be able to track work across both platforms seamlessly.
What this means for your company
You can cut out redundant work: You no longer have to manually create and link a corresponding ticket in Jira for a Thoropass action item.
You can meet the tech team where they are: Employees that typically work within Jira can continue to manage their Thoropass assignments on that same platform.
Your compliance initiatives will always be in sync: Completing an action item in Thoropass or closing the corresponding ticket in Jira will sync back and forth, so you won't need to do any manual follow up.
Read more below on:
1. Setting up the Connection
For a walkthrough with screenshots, visit the article on How to Set Up the Jira for PM Sync page.
Navigate to the Integrations page and select "Jira (for PM Sync)".
Walk through the wizard to input the information needed to connect to Jira and grant Thoropass the read & write permissions we need to integrate with your Jira instance.
Wait until your Jira Projects and Issue types are pulled into Thoropass.
Select the Jira project that will be the destination of every ticket originating in Thoropass.
Select the default ticket type for each ticket that Thoropass will create from our action items.
2. Syncing Action Items
Any action item can be sent to the Jira project you configured in the Integration wizard.
From a controls page, select "Sync All Action Items" or "Send to Jira" on an individual action item. Confirm that you'd like to send the action item(s) to Jira.
When sending an action item to Jira for the first time
A Jira ticket will be created in the project you specified in the Integration Wizard with the default ticket type you specified in the Integration Wizard
The action item title becomes the ticket title with "[Thoropass]" added to the beginning
The action item description becomes the ticket description
The action item due date (if due date exists as a field in your project) is sent from Thoropass to Jira. It does not sync back, so any changes to due date in Jira will stay in Jira.
The assignee field is NOT populated in Jira. The owner of the action item in Thoropass does not change the assignee in Jira.
Any attachments on the action item will be sent to Jira and synced back and forth
A comment is added to the Jira ticket explaining the origin of the ticket (Thoropass) and the syncing behavior (see screenshot below)
Ongoing syncing: Thoropass action item <> Jira ticket
What is synced between Thoropass and Jira?
Status: If an action item is completed in Thoropass, the ticket will be closed in Jira. If a ticket is resolved in Jira, the action item will be completed in Thoropass.
Attachments: An attachment added to a Jira ticket will be uploaded to the Thoropass action item and vice versa; if the attachment is deleted in Jira, we will delete it from the action item. One exception; we cannot delete attachments in Jira, so to delete an attachment in Thoropass that has been added from Jira, you must delete it in Jira.
What data is only sent one-way?
Action item title and description
Due date
The action item title, description, and due date is only sent from Thoropass to Jira.
What is not not synced?
The Thoropass owner does not become the Jira Assignee; the two fields remain separate.
Your organization may want to configure rules/automation within Jira to assign the ticket to the right person using a condition like contains "[Thoropass]" in the title.
"Unsyncing" an Action Item or Disconnecting the Connection Account
To stop the connection between Thoropass and Jira, there are two options:
(1) Unsync an individual action item
This action can be performed on action items that are incomplete: navigate to the action item, click "Synced to Jira" to see the drop-down menu, and select "Unsync".
The unsync action removes the connection between the action item and ticket.
Nothing changes in the ticket.
The action item will show the option to Sync to Jira again; selecting that action will create a new ticket in Jira.
(2) Unsync all action items by Disconnecting or Reconfiguring the Connection Account
To remove the connection between all action items and all corresponding Jira tickets, remove the connection account on the Integrations page.
Navigate to the "Jira (for PM sync)" integration page and select Remove or Reconfigure.
Select "Remove" to remove the connection completely.
Select "Reconfigure" to update the Jira information (if you moved to a new Jira instance, for example).
When you reconfigure the connection account, if you select the same project and issue type that you had before, you are able to re-sync the existing action items linked to Jira tickets. The Jira ticket will be the source of truth for any discrepancies; if the action item and ticket differ in status, the Jira ticket will overwrite the action item.