Learn about Savio
- Getting Started
- How Savio Works
- Triaging Feedback
- Managing Users
- Closing the Loop
- Voting Boards
- Importing People, Companies, and Attributes
- Connecting Your Support Tool
- Chrome Extension
- Emailing Feedback
- Slack Integration
- Creating Feedback Templates
- Tips for Triaging Effectively
- Managing Custom Attributes
- Canned Filters
- Hubspot Integration
- Importing Historical Data
- Using Savio's API
- Setting “Feedback From”
- Exporting Your Data
- Feature Request Details Page
- Setting Up Savio
- How To Be Successful with Savio
- The Four Problems Savio Solves
- Segment Integration
- Help Scout Integration
- Zendesk Integration
- Intercom Integration
- Salesforce Integration
- Customizing Feature Request List Columns
- Customizing Feature Request Status Options
- Moving Feedback
- Savio's Integrations and Their Features
- Daily Digest Email
- Running a Product Meeting
- Zapier Integration
- Voting on Behalf of (VOBO)
- Single Sign-On
- Configuring Voting Board Access
- Using Feedback Forms
- The My Feedback Page
- Using Tags
- Filtering Feedback and Feature Requests
- Jira Integration
- → Shortcut Integration
- Using the Zendesk App
How to Set Up Savio’s Shortcut Integration
Savio collects customer feedback, tracks your feature requests, and makes it easy to prioritize features based on what your customers want.
But once you’ve decided on your roadmap, the features go to your Devs to be built. And they probably use a project management tool like Shortcut. The problem becomes keeping track of the status of those features. For example, your customer-facing teams using Savio may want to know when a feature has been shipped without going into Shortcut or sending an email constantly asking Devs for updates.
That’s where the Savio Shortcut integration comes in. The integration links feature requests in Savio with corresponding stories in Shortcut. Then, anytime the story changes status in Shortcut, its status is automatically updated in Savio.
In this article, we explain how to set up the Shortcut integration and how it works. We’ll cover:
Why set up the Shortcut integration?
If you do not connect Shortcut to Savio, your customer-facing teams end up relying on communication with the Dev team to know the status of features. It adds in busywork: more Slack messages, more emails, or more interruptions at the Dev’s desk. Or, if your Devs are particularly proactive, they have to send out status updates or even go into Savio to update the status of a feature.
The value of the Shortcut integration is that this communication is automated:
When a Dev changes the status of a story in Shortcut, the status gets automatically updated in Savio.
As an example, this “Android App 2.0” feature request has an “Untriaged” status in Savio.
Now, imagine one of your developers moves the “Primary” story for that feature request to “Planned” in Shortcut.
In Savio, you’ll see the Shortcut story status updated in the feature request.
You’ll see that the feature request’s status is also updated to “Planned” in Savio.
The result is more seamless communication. Your teams using Savio always know the status of a feature, and your Dev’s have fewer tasks in their workflow and fewer emails.
How to set up the Shortcut integration
First, we’ll connect Savio to Shortcut using Shortcut’s API. Next, we’ll set up a webhook so that when a story’s status changes in Shortcut, it’ll also be changed in Savio.
Connect Savio to using Shortcut’s API
1. Log into Savio, and navigate to “Integrations”.
2. Click “Connect Shortcut”.
3. Navigate to your Shortcut workspace. Click “Settings”, then “Your Account”, and then “API Token”. Name the token and click “Generate Token”.
4. Copy the resulting API token.
5. Navigate back to Savio. Paste the API token in the “API token” field and click “Save”.
Read more: Shortcut API Tokens
Connect Savio to using Shortcut’s API
Now Savio is connected to Shortcut’s API. Next, we’ll set up a webhook so that when an issue’s status changes in Shortcut, it also changes in Savio.
1. Navigate to “Integrations” in Shortcut.
2. Choose “Webhooks”.
3. Copy the “Payload URL” and “Secret” fields from Savio.
4. Paste the “Payload URL” and “Secret” fields into Shortcut.
Now you’ve finished connecting Savio to Shortcut.
Map Shortcut story status to Savio feature request status
The next step is to map statuses. You’ll see a list of the statuses that exist for your teams on the left, and the feature request status options in Savio (on the right).
Tip: You may have several teams working in Shortcut. To link up with the Dev team, make sure you are changing the Dev team’s statuses.
Choose the Savio statuses that correspond with each Shortcut story status. Choose “Do Nothing” to keep a feature request’s status the same in Savio when the story moves to the specified Shortcut story state.
Tip: We like to connect Shortcut to Savio in the following way:
We link our “Someday Maybe” story to our “Under Consideration” status in Savio;
our “Planned” Shortcut status with our “Planned” status in Savio;
our “In Development” Shortcut status to our “In Progress” status in Savio;
and our “Completed” status in Shortcut to our “Shipped” status in Savio.
How to link a Savio feature request to a Shortcut story
So now the integration is set up. You can now link a feature request in Savio to a story in Shortcut. Here’s how to do that:
1. Navigate to the feature request you’d like to link with a Shortcut story. Click “Feature Requests” in the left navigation menu and then click the title of the feature request you’d like to link with Shortcut.
2. Click “+ Link to Shortcut Story”.
Then you can choose to either create a new story in Shortcut or to link to an existing Shortcut story.
Create and link to a new Shortcut story
If you want to create a new story in Shortcut to link a feature request to, click the “Create and Link to New Story” tab.
Then fill in the fields:
Summary: This is the title of the story that will be created in Shortcut. This is a required field.
Description: This is the description that will be created in the Shortcut story.
Update the linked feature request’s status when this story’s status changes: Checking this box will make the linked Shortcut story the “Primary” story. That means that the Savio feature request will have its status updated when the linked Shortcut story’s status changes. When unchecked, this feature request in Savio will not be updated when the linked Shortcut story has its status changed.
Note: For each Savio feature request, only one Shortcut story can be a “Primary” story and have the “Update the linked feature request’s status when this story’s status changes” box checked. If another story already has been set to control the Savio feature request status, this box will be greyed out. If you check it when it is greyed out, you’ll make the current story the “Primary” story.
When you have filled in the fields, click the “Create Shortcut Story and Link” button. You’ll see the story linked on the feature request page.
Link to an existing story
If you want to link to a story that already exists in Shortcut, click the “Link to Existing Story” tab.
Then fill in the fields:
Shortcut Story: Select a story from this list of your existing Shortcut stories.
Update the linked feature request’s status when this issue’s status changes: Checking this box will make the linked Shortcut Story the “Primary” story. That means that the Savio feature request will have its status updated when the linked Shortcut story’s status changes. When unchecked, this feature request in Savio will not be updated when the linked Shortcut story has its status changed.
When you have filled in the fields, click “Link to Shortcut Story”.
You’ll see the issue linked on the feature request page.
You might have some feature requests in Savio that are related to several different Shortcut stories. We’ve developed the integration to allow you to link a feature request in Savio to more than one Shortcut story.
However, there is always only one “Primary” story. The “Primary” story is the one that controls the status of the feature request in Savio. So, while the different Shortcut stories may move through the development workflow at different rates (and each story could have a different status), the feature request’s status in Savio follows only the “Primary” story’s status.
The “Primary” story is the story that is bolded in the Linked Shortcut Stories list.
Tip: If you have multiple Shortcut stories linked to a Savio feature request, we suggest making sure that the “Parent” Shortcut story (the most important story) is set to be the “Primary” story—the one that controls the Savio feature request status.
How to make a story the “Primary” story
To set an issue to be the “Primary” story, do the following:
1. Hover your mouse over the story and click the “Edit Primary setting” icon.
2. Select “Update the linked feature request’s status when this story’s status changes. Then click “Save”.
Now that story is the “Primary” story. When the Shortcut status of that story is changed, the status of the linked feature request in Savio will also change; other linked Shortcut stories will not affect the status in Savio.Last Updated: February 23 2021