Fathom to Jira
Fathom records the call, but someone still has to turn it into Jira tickets, and tasks get missed or assigned to the wrong person on the way. Spectr reads the call, drafts a Jira story with acceptance criteria and an estimate for each requirement and bug, and publishes them to Jira.
How it works
A call is imported from Fathom. Spectr picks out a requirement, a bug, an action item and an out-of-scope ask, and drafts a story and a bug with acceptance criteria. A person approves both, they are published to Jira, and the requirements, scope log and project memory update from the same call.
Fathom connects with an API key you create in your Fathom account settings. Jira connects through Atlassian's OAuth 2.0 (3LO) consent screen, where you choose which Jira Cloud site Spectr may publish to.
A Jira Cloud site. Jira Server and Data Center are not supported. On the Fathom side you need only the API key.
Copy Fathom action items straight into Jira and you get one-line summaries with no type, no acceptance criteria and no background. That is why the questions start on Monday. Spectr drafts stories from the call's requirements and bugs instead, each with the reason it came up, criteria a tester can check and an estimate.
Fathom is the one note-taker that exports action items as structured data rather than prose. Spectr files them as their own section of the meeting record, and extraction has to account for every entry, so "send the revised SOW to legal" cannot drop out before the spec sheet is written.
Drafts are matched to the issue types your chosen project really has: features become Stories, defects become Bugs, chores and spikes become Tasks. Priority is matched by name to your own scheme, and the estimate goes into your story-points field when the site has one.
When the spec marks a task from the call as a parent, Spectr creates a parent issue for it and nests its stories beneath as real Jira sub-tasks. A project without a sub-task type gets the same stories published flat instead of a failed publish.
In Spectr, open the project you want to connect and go to Integrations.
In Fathom, create an API key from your account settings.
Choose Fathom and paste the key.
Choose Jira, click Connect, and pick the site on Atlassian's consent screen.
Pick the Jira project new issues should land in - and optionally a default issue type and starting status.
Import a meeting from Fathom. Spectr gathers project context, extracts a structured spec, and drafts a story for each requirement and bug.
Approve the drafts you want and publish. They appear in your Jira project as typed issues, and each story in Spectr links to the issue it became.
Anything else? Email hello@crowdlinker.com and a person will answer.
Not directly. Fathom's built-in task integration is Asana, so the usual route to Jira is a Zapier template that creates one issue per action item. Spectr connects to Fathom with an API key, which every Fathom plan includes, and to Jira Cloud over OAuth.
One you pick at setup, per Spectr project. You can also set a default issue type and the workflow status new issues should start in.
Yes. Whenever you refresh story status from the Stories or Budget page, Spectr reads each published issue's status category and rolls it up onto the story, which is also what feeds the budget projection.
No. Spectr connects to Jira Cloud only, through Atlassian's OAuth.
Use case
Import a call, get a draft backlog, approve what is right
Import a Fathom call and get structured specs and stories from its notes, action items, and transcript
Publish stories as Jira issues, with sub-task nesting, and read their status back
