How to Set Up Savio’s Jira Integration

Product and Customer Success teams use Savio to centralize customer feedback and feature requests, choose which features to prioritize, and more. But the Devs actually building the features are more likely to be using other tools that are specifically designed to facilitate the development process—tools like Jira.

We’ve built an integration with Jira that makes it easy for Dev teams to automatically update the status of a feature request in Savio. The integration means Product and CS teams can see the current status of a feature request without having to contact their Dev team. 

In this article, we explain how to set up the Jira integration and how it works. We’ll cover:

Why set up the Jira integration?

Without this integration, you have to update the status of a feature request manually in Savio. It’s not hard to do, but it adds in some extra busywork: Product or CS has to reach out to the Dev team to get an update on a feature’s status. Then they have to manually update the status in Savio.

The beauty of the Jira integration is that it automates that process: 

When a Dev changes the status of an issue in Jira, the status gets automatically updated in Savio. 

This integration facilitates communication between the Dev team, Product, and CS. It means you don’t have to constantly ask your Dev team what the status of a feature request is. 

How to set up the Jira integration

The Jira integration is currently available on all paid plans. To set up the integration, do the following:

1. Log into Savio, and navigate to “Integrations”. 

2. Click “Connect Jira”.

3. Click “Accept’ to allow Savio access to your Jira account.

You’ll be shown a mapping between the issue states you’ve specified in Jira (on the left) and the feature request status options in Savio (on the right). 

Note: You can customize your statuses in both Jira and in Savio. Learn more about customizing issue statuses in Jira or about customizing feature request statuses in Savio

4. Choose the Savio statuses that correspond with each Jira issue status. Choose “Do Nothing” to keep a feature request’s status the same in Savio when the issue moves to the specified Jira issue state.

Tip: We like to connect Jira to Savio in the following way:

  • We map our “Selected for Development” status in Jira to our “Planned” status in Savio;

  • our “To Do” Jira status with our “Planned” status in Savio; 

  • our “In Progress” Jira status to our “In Progress” status in Savio; 

  • and our “Done” status in Jira to our “Shipped” status in Savio. 

How to link a Savio feature request to a Jira issue

Once you’ve set up the integration and mapped Jira issue statuses with Savio feature request statuses, you can link individual Jira issues to feature requests in Savio. Here’s how:

1. Navigate to the feature request you’d like to link with a Jira issue. Click “Feature Requests” in the left navigation menu and then click the title of the feature request you’d like to link with Jira.

2. Click “+ Link to Jira Issue”. 

Then you can choose to either create a new issue in Jira or to link to an existing Jira issue.

Create and link to a new Jira issue

If you want to create a new issue in Jira to link a feature request to, click the “Create and Link to New Issue” tab. 

Then fill in the fields:

  • Project: Choose the Jira project into which you want to create a new Jira issue. This is a required field. The options will be the list of projects you have in your Jira account.

  • Issue type: Choose the issue type for the issue you will create. This is a required field. The options will be a list of issue types that you have specified for your Jira account.

  • Summary: This is the title of the issue that will be created in Jira. This is a required field.

  • Description: This is the description that will be created in the Jira issue. 

  • Update the linked feature request’s status when this issue’s status changes: Checking this box will make the linked Jira issue the “Primary” issue. That means that the Savio feature request will have its status updated when the linked Jira issue’s status changes. When unchecked, this feature request in Savio will not be updated when the linked Jira issue has its status changed. 

Note: For each Savio feature request, only one Jira issue can be a “Primary” issue and have the “Update the linked feature request’s status when this issue’s status changes” box checked. If another issue already has been set to control the Savio feature request status, this box will be greyed out. If you check it, you’ll make the current issue the “Primary” issue.

When you have filled in the fields, click the “Create Jira Issue and Link” button. You’ll see the issue linked on the feature request page.

Link to an existing Jira issue

If you want to link to an issue that already exists in Jira, click the “Link to Existing issue” tab.

Then fill in the fields:

  • Jira Issue: Select an issue from this list of your existing Jira issues.

  • Update the linked feature request’s status when this issue’s status changes: Checking this box will make the linked Jira issue the “Primary” issue. That means that the Savio feature request will have its status updated when the linked Jira issue’s status changes. When unchecked, this feature request in Savio will not be updated when the linked Jira issue has its status changed. 

When you have filled in the fields, click “Link to Jira Issue”.

You’ll see the issue linked on the feature request page.

“Primary” issues

You might have some feature requests in Savio that are related to several different Jira issues. We’ve developed the integration to allow you to link a feature request in Savio to more than one Jira issue.

However, there is always only one “Primary” issue. The “Primary” issue is the one that controls the status of the feature request in Savio. So, while the different Jira issues may move through the development workflow at different rates (and each issue could have a different status), the feature request’s status in Savio follows only the “Primary” issue’s status. 

The “Primary” issue is the issue that is bolded in the Linked Jira Issues list.

Tip: If you have multiple Jira issues linked to a Savio feature request, we suggest making sure that the “Parent” Jira issue (the most important issue) is set to be the “Primary” issue—the one that controls the Savio feature request status. 

How to make an issue to be the “Primary” issue

To set an issue to be the “Primary” issue, do the following:

1. Hover your mouse over the issue and click the “Edit Primary setting” icon. 

2. Select “Update the linked feature request’s status when this issue’s status changes. Then click “Save”.

Now that issue is the “Primary” issue. When the Jira status of that issue is changed, the status of the linked feature request in Savio will also change; other linked Jira issues will not affect the status in Savio. 

How a Savio feature request status is changed through Jira

When your integration is set up and you have linked a Savio feature request to a Jira issue, your team can change the status of a feature request directly from Jira. Here’s how that works. 

As an example, this “Streak CRM Integration” feature request has a “Planned” status in Savio.

Now, imagine one of your developers moves the “Primary” issue for that feature request to “Done” in Jira.

In Savio, you’ll see the Jira status updated in the feature request.

You’ll see that the feature request’s status is also updated to “Shipped” in Savio.

Last Updated: January 24 2021