Issue trackers

Used with cascade ticket <provider>:<id> to fetch a ticket and run it through the pipeline.

Supported

Tracker	Identifier format	Example
GitHub Issues	github:owner/repo#N	github:myorg/myrepo#42
Jira	jira:KEY-N	jira:PROJ-123
Linear	linear:KEY-N	linear:ENG-456
Azure DevOps Boards	azure_devops:org/project/N	azure_devops:myorg/myproj/123
GitLab Issues	gitlab:group/project#N	gitlab:myteam/myrepo#42

Setup

GitHub Issues

cascade configure issue github --token ghp_xxx

Same token used by the GitHub VCS provider; just register it for issues too.

Jira (Cloud)

cascade configure issue jira \
  --token JIRA_API_TOKEN \
  --base-url https://yourcompany.atlassian.net \
  --user you@yourcompany.com

Create the API token at https://id.atlassian.com/manage-profile/security/api-tokens.

For Jira Server / Data Center, set --base-url to your server.

Linear

cascade configure issue linear --token lin_api_xxx

Token from https://linear.app/settings/api.

Azure DevOps Boards

cascade configure issue azure_devops --token your_pat

PAT needs Work Items (Read) scope.

GitLab Issues

cascade configure issue gitlab --token glpat-xxx
# Self-hosted:
cascade configure issue gitlab --token glpat-xxx --base-url https://gitlab.acme.io

Token needs api scope.

What gets imported

For each tracker, Cascade pulls the ticket and converts it into a Story:

• Title from the ticket title
• Description from the ticket body (Jira ADF flattened to text; Linear and GitHub markdown preserved)
• Acceptance criteria synthesized as one placeholder criterion. Edit the story in cascade review before building if you want richer criteria.
• Status set to APPROVED automatically (tracker tickets are assumed pre-approved by the team that ticketed them)
• Source link included in the story notes and the PR description

When tickets aren’t enough

Tracker tickets often lack technical detail. For those, two options:

1. Add detail to the ticket before running Cascade. The richer the ticket, the better the output.

2. Use a prompt instead, supplying the technical context directly:

   cascade prompt "Implement PROJ-123 (cursor pagination on /api/users): use ?limit (default 50, max 200) and ?after (last seen ID), wrap responses in {data: [...], cursor: '...'}"

Coming in v0.2

• Bulk import: cascade ticket --query "project = PROJ AND status = 'To Do'" to ingest a backlog
• Bidirectional sync: post a comment on the ticket when the PR opens, update status when the PR merges
• ClickUp, Asana, Shortcut, Trello as additional trackers