Sightdeck AI

User Guide

Track Jira tickets

Your work items live in Jira, but you want Claude to actually do them. Here's how to pull a Jira ticket into Sightdeck AI, run it on its own Git branch, and report back automatically when it's finished.

Before you start

You need a project added in Sightdeck AI and a Jira ticket to work from — the ticket key (like AHSR-1234) and its URL are enough. The Git and webhook steps are optional; do the ones that fit your setup.

Steps

  1. Bring the ticket in. Create the task from the Jira ticket — Sightdeck AI stores the ticket key and URL on the task so the card links straight back to Jira. How the external reference is captured and shown is covered in Jira integration.
  2. Let it refine. The task refines like any other — title, summary, kind, estimate — while keeping the Jira reference attached. See Backlog refinement for what gets filled in.
  3. Run it on its own Git branch. Turn on the per-task Git branch so the work is isolated and easy to review before merging — the default branch option is enough; worktrees are an advanced setup you can ignore for now. Both are covered in Git branches & worktrees.
  4. Report back on done. Wire a webhook so that when the task reaches done, Sightdeck AI notifies your other tools — a Slack channel, a CI job, or a service that moves the Jira ticket. Set it up via Webhook on done.

What you get

  • A Sightdeck AI task that links straight back to its Jira ticket, so you never lose the origin.
  • Isolated, reviewable work on a dedicated branch instead of loose changes on your main line.
  • An automatic signal back to your stack the moment the work is finished.
Sightdeck AI integration settings for Jira, Git and webhooks
Jira reference, Git branch and webhook-on-done wire a ticket end to end.