Tickets Hub docs

Specs into delivery tickets

Tickets Hub turns uploaded or pasted product specs into developer tickets, GitHub issues, milestones, and Projects placement. Confluence and Jira sync are optional Atlassian add-ons.

Setup

GitHub App

Install the GitHub App and add delivery repositories so issues can be created in the right repos.

Atlassian OAuth

Connect Atlassian from Account only if you want Jira or Confluence sync. Users do not paste API tokens.

Spec-run credits

Free workspaces include 10 spec runs. Buy one-time Stripe packs when the workspace needs more.

Workflow

  1. 1

    Create a spec job

    Upload or paste a spec, select a GitHub repository, and optionally include a Confluence page reference.

  2. 2

    Create tickets

    The job returns epics, stories, tasks, acceptance criteria, labels, and dependencies.

  3. 3

    Sync GitHub

    Tickets are created in GitHub. Milestones are created or reused from the spec title, and Project placement runs when configured.

  4. 4

    Sync Atlassian when configured

    Connected workspaces can also publish Confluence pages and create Jira issues from the same tickets.

Delivery targets

Confluence Optional canonical spec page for teams with Confluence.
Jira Optional delivery issues in a selected Jira project.
GitHub GitHub issues, milestones, and optional Projects v2 membership.

Troubleshooting

Atlassian connect fails

Confirm the Atlassian Developer Console callback URL exactly matches the configured redirect URI and that the app has Jira, Confluence, and offline access scopes.

Jira project cannot be found

Open the GitHub repository settings from Account or the new spec page, then link that repository to a Jira project visible to the connected Atlassian account. Jira tickets are created only for spec jobs whose selected repository has this project link.

GitHub tickets were created but Jira was skipped

This means Atlassian is connected but the selected repository has no Jira project link. Save a Jira ticket target in repository settings, then run a new spec job against that repository.

Generated tickets need edits

Run the job in review mode. Draft edits are stored locally before external sync.