Issue trackers

Publish approved user stories straight into Shortcut

Spectr drafts the stories. Shortcut is where the approved ones go. Connect a Shortcut workspace with an API token, pick the team, and each approved story arrives with its description, acceptance criteria, estimate, tags and assignee already set. Spectr reads each story's workflow state back, so your delivery and budget numbers reflect what is really done.

How it connects

API token. You create a token in Shortcut and paste it into the project, then pick the team and the workflow state new stories should land in.

Before you start

No plan requirement. Connections are configured per project, and every credential is encrypted at rest.

What Spectr reads from Shortcut

Teams and workflows: Read at setup so you can choose the team and the default workflow state new stories are created in.
Workflow state of published stories: Read per story and mapped through your workspace's own workflow columns onto done, in-progress or unknown. A story deleted in Shortcut keeps its last known state rather than being wiped.
Tags: Tags applied in Shortcut sync back onto the Spectr story, with the internal priority pseudo-label filtered out.

What Spectr writes to Shortcut

Stories, only after approval: Nothing reaches Shortcut until a person approves it in Spectr's review step.
Estimates, tags and assignee: Mapped onto Shortcut's own fields, with story type resolved from Spectr's feature, bug, chore and spike classification.

A person approves everything before it is published

Spectr generates specs and stories, then stops. Every story goes to a review page where you approve it, edit it inline, or reject it - individually or in bulk. Only approved stories reach an issue tracker. There is no auto-publish setting to switch on, because a backlog nobody read is not a saving.

Setting it up

In Shortcut, create an API token from your account settings.
In Spectr, open the project, go to Integrations, choose Shortcut and paste the token.
Select the team new stories should be created in, and the workflow state they should start in.
Generate stories from a meeting and review them.
Publish the approved stories. Each one links back to its Spectr story.