Sync your Jira issues as Custom Objects. You can seamlessly manage and track issues between Vitally and Jira.

About Jira

This bidirectional synchronization lets you pull all Jira Issues as Custom Objects into Vitally. Additionally, you can create new Jira issues in Vitally, update existing ones, and synchronize them back to Jira. You can either create a Table View or view them while in an Account 360 to keep up to date on any Jira Issues right within Vitally.

We will import the last 12 months of Jira Issues on the initial integration.

Please note that the Reporter field is assumed to hold internal user email addresses. If you are adding end-user email addresses to this field, we will auto-create internal users from those email addresses.

Jira: How to Enable

How ToHow To Visual
  1. Navigate to your Settings (⚙️) by selecting your Account Logo on the top left

  2. Scroll down to Data Management and select Integrations (or get there via Quick Jump CMD+J)

  3. Click on the Jira tile and toggle the switch in the upper right to get started

  4. Enter your Jira base URL. To find this, access any Jira ticket and copy the URL up to and including "atlassian.net" (e.g. "https://my-site.atlassian.net")

  5. Once you paste this into Vitally click the Set Base URL button to proceed.

  6. Click Connect to Jira to be redirected to the Jira Marketplace

  7. Click Get it now and then Get started to install the Vitally App in your Jira instance

  8. Click the head back over to Vitally link to start configuring what data to sync

Now you can start adding your Jira Issues on the Vitally configuration Jira page:

  1. Select Add a new Custom Object

  2. Provide JQL to specify the type of issues you want to track. JQL validation will occur before you proceed with the following steps of the configuration

    • Paste that JQL query in Vitally under "Please enter valid JQL."

  3. Name the issues you want to track, such as "high priority bugs" for example

  4. Specify which traits have Customer information, like Organization or Account external ID. While all external ID fields are optional, you must at least configure one External ID Property. See the FAQ below for what field types are supported as External IDs. We first try to link via Account or Organization external ID, if that is unsuccessful we try by User external ID, if that is still unsuccessful we then try user email (if present)

  5. Select which team member will have permission to create new Jira issues in Vitally and synchronize them back to Jira To create new Jira issues in Vitally, you should link via Account or Organization ID

  6. Now you can select the traits (fields) that you want to pull into Vitally such as Issue Type, priority, status, etc; and set the relevant editing permissions If you select 'no one' to allow edits, that means Vitally can't make updates. Updates can only be done in Jira.

  7. Repeat steps as necessary until all your Jira Issues are configured to bring into Vitally

External ID's are all optional but you must configure at least one External ID to link the Issues in Vitally to an Account or Organization.

When issues no longer match the JQL filter criteria, they become stale within Vitally. Vitally will archive these issues within 24 hours.

Jira: Errors and Troubleshooting

If you are unable to complete the Jira installation due to an error, you can follow the troubleshooting steps below to re-install the Vitally app. If any errors persist, please reach out to our Support team at support@vitally.io or via the in-app chat!

  1. Open Jira and navigate to Apps > Manage your apps

  2. In the User-installed apps section, expand the Vitally app

  3. Click Uninstall

  4. Follow the Jira: How to Enable steps above to re-install the Vitally app

Jira FAQ

Q: Is Jira bidirectional? A: Yes! you can create new Jira issues in Vitally, update existing ones, and synchronize them back to Jira

Q: Do these roll up to the Account+Organization level? A: Yes!

Q: Can I include more than one project in one JQL filter? A: No, it's only one project per a JQL filter. If you wish to add in further projects via another JQL filter, then you would need to create a new custom object where an additional JQL filter can be applied.

Q: What Jira field types can I use as an External ID property? A: Text, Numbers, Select List (multiple choice), or Select List (single choice)

Q: An auto-created User is appearing in Vitally from a Jira ticket, why is this? A: If the User being created is set as the Reporter on the Jira ticket, then they will be created as an auto-created in Vitally.

Last updated