01
PlanStart with the Jira goal
Task intent, acceptance criteria, assignment, and delivery state stay authoritative.
Loading Vectras.
Loading Vectras.
Connect delivery intent, repository evidence, assistant activity, and review decisions in one operating view.
Jira owns the goal, acceptance criteria, and delivery state.
Vectras keeps planning, active changes, commits, reviews, and Jira state in the same task-level record.
Task intent, acceptance criteria, assignment, and delivery state stay authoritative.
Code with any assistant, push a branch, and Vectras reads the diff straight from GitHub.
Your connected AI drafts the commit in the Vectras template; the verified merge becomes evidence.
Approval triggers the configured Jira transition and records the outcome.
Pending changes stay pending. Commits become evidence only after the provider confirms them, and completion remains a review decision.
Repository, branch, files, and commit references stay attached to the Jira task.
Overview shows where every task stands. Tasks hold the working context and branch review. The Review Hub queues what needs a decision. Activity and Admin Diagnostics keep the trail auditable.
Enter the productConnect Jira, GitHub, and your own OpenAI, Claude, or Gemini accounts.
Vectras reviews pushed branches through the GitHub App - no source is stored.
Workspace isolation and per-project, per-repository grants are enforced by the API.