Your first Run

Trigger a run manually

Go to New pipeline run (linked from the dashboard) and fill in three things:

1. Jira ticket key — e.g. PROJ-1234. PilotX doesn't validate this against Jira; any value your team recognizes works.
2. Target repository — pick from the repositories you've watched under GitHub, GitLab, or Bitbucket.
3. Target branch — defaults to the repository's default branch; change it if you want the run to target something else.

Click Trigger pipeline. Scout through Reporter run as one continuous action — this typically takes a few seconds to a couple of minutes depending on ticket/repo size — and you're taken straight to the run's detail page, where you can watch each stage complete.

Let Jira trigger a run for you

Once a Jira project is connected, PilotX can pick up tickets without anyone opening the trigger-run screen:

• Comment command — post a comment containing /qa-test PROJ-1234 on a watched ticket (or any ticket, followed by the key) and PilotX creates a run for it.
• Status transition — configure an auto-trigger status on a watched Jira project (e.g. "Ready for QA") under its project settings; any ticket that transitions into that status starts a run automatically.

Both paths create the run the same way the manual trigger screen does. The status-transition trigger is deduplicated — if a run for that exact ticket is already in progress, a repeat transition into the configured status is a no-op rather than a duplicate run.

What happens after

If your workspace is in full-auto gate mode, the run proceeds straight through to Runner and Reporter. If it's human-gated, the run pauses after QA Reviewer and waits for an Admin to approve or reject it from the run detail screen — see Human gate & approvals.

Either way, Reporter posts a summary to your connected Slack workspace (if you've connected one) once the run finishes, and the full report is always available on the run's detail page.