TestingOps.ai

Issue trackers, wikis and code · Native connection

Jira and TestingOps: AI test agents in your Jira workflow

Jira is more than the place defects end up. TestingOps reads your stories into its knowledge base, lets AI test agents refine them and write test cases from their acceptance criteria, and acts on the workflow steps you choose.

  • Native connection
  • Available
Request a demo Tester Agent for Jira documentation
Connection
Native connection
Writes back
Within what you allow
Last checked
7 Nov 2026

In short

Jira and TestingOps in short

The Jira connection brings the work items of a linked Jira project into the TestingOps knowledge base as requirements, and lets the TestingOps Tester Agent act on Jira events such as a status change.

Agents use stories and their acceptance criteria to propose refinements, write draft test cases, select the tests a change affects and run them, then comment the result on the issue.

You connect with an API token or Atlassian sign-in, and can pair the TestingOps Tester Agent app for Jira Cloud. What agents may write is limited by a switch on the link and by the rules you set.

What it does

What it does for your testing

  1. 1

    A story becomes test context

    Input
    A user story with an "Acceptance criteria" section
    TestingOps
    Stores it as a requirement in the project's knowledge base; agents search it when they write or review test cases
    Output
    Test cases that trace back to the Jira item
  2. 2

    A thin story gets refined

    Input
    An item that reaches your refinement step
    TestingOps
    Proposes a standard user story, 3–8 Given/When/Then acceptance criteria and up to six open questions, from the item and the nearest knowledge-base entries
    Output
    A proposal comment you approve, edit or reject; approved text goes into managed sections of the description
  3. 3

    Criteria become draft cases

    Input
    Approved acceptance criteria
    TestingOps
    Writes draft test cases so that every criterion is checked by at least one case
    Output
    Reviewable cases linked to the Jira requirement, including the negative or edge scenario the criteria name
  4. 4

    A move to Test starts the right tests

    Input
    An issue moved to your test column
    TestingOps
    Finds commits and branches that carry the issue key in up to five linked repositories, the test cases they affect and the cases linked to the requirement, and runs them
    Output
    A result comment on the issue and, if all pass and your rules allow it, a transition

Step by step

How it works

  1. Connect JiraUse Connect Jira: sign in with Atlassian, or enter your site, account email and API token. Jira Server and Data Center use a personal access token.
  2. Link a projectLink the Jira project to a TestingOps project. Each sync reads its 300 most recently updated items, optionally narrowed by a JQL filter inside that project; syncs run hourly and on Sync now.
  3. Pair the Jira app (optional, Jira Cloud)Install TestingOps Tester Agent in Jira and paste a one-time setup code from TestingOps. The app delivers Jira events without a site webhook and writes comments as the app.
  4. Describe what agents do at each stepIn Board rules, write one sentence per column, for example what happens when an item reaches Test. Rules run in suggest, approve or autonomous mode, with limits such as allowed transitions and a maximum number of cases.
  5. Agents act and run testsOn a matching event, agents refine the item, write cases, analyse impact and start a run on your execution provider (RunningOps on testingops.ai).
  6. Results return to the issueProposals, run results and regression changes appear as comments, and transitions happen only to states your rules allow.

Writing to Jira needs the link's "Agents may write to this tracker" switch, and autonomous rules must list the transitions they may make.

Connect

Setup

  1. In TestingOps, open Integrations → Project tools and select Connect Jira.
  2. Choose Sign in with Atlassian, or enter your Jira site, account email and API token (Server and Data Center: a personal access token).
  3. Pick the Jira project to link; the first sync starts. Turn on "Agents may write to this tracker" if agents should comment or transition.
  4. Optional, Jira Cloud: under Jira app select Generate setup code, install TestingOps Tester Agent in Jira and paste the code in Apps → Manage apps → TestingOps. The connection then shows Paired.
  5. Open Board rules, describe what the agent should do in each column, check the preview and select Finish setup.

Documentation: Tester Agent for Jira documentation

Where you connect it in TestingOps: Integrations → Project tools → Issue trackers, wikis and code → Connect Jira

Use cases

Use cases

Refine a story before sprint planning

Trigger
An item reaches your refinement column, or someone mentions the agent on it
Uses
The item text and the six nearest knowledge-base entries
Agent activity
Proposes a user story, Given/When/Then acceptance criteria with at least one negative or edge scenario, and open questions where the item does not say enough
Result
A proposal comment; on approval, managed sections in the description while the author's own text stays above them
Condition
Approve mode is the default

Write test cases from acceptance criteria

Trigger
Acceptance criteria are approved
Uses
The criteria in the description's Acceptance criteria section
Agent activity
Writes draft cases so that every criterion is verified by at least one case and nothing beyond the criteria is assumed
Result
Draft cases linked to the Jira requirement, ready for review
Condition
Boundary values are not generated as a separate step

Test what a change touched when an item reaches Test

Trigger
A status change to your test column
Uses
Commits and branches that carry the issue key (last 90 days, up to five linked repositories) and the cases linked to the requirement
Agent activity
Selects the affected cases, runs them and comments the outcome
Result
A run result comment with pass and fail counts and a link to the run; an optional transition when everything passes
Condition
Needs Jira events (the app, the Data Center plugin or a site webhook) and the issue key in commit messages or branch names

Keep the regression set current

Trigger
The impacted tests pass
Uses
The passing cases of the run
Agent activity
Adds them to a regression plan; while the change is unmerged they wait as candidates tied to the item
Result
A regression plan that follows merged changes
Condition
In approve mode the agent asks before changing the set

Capabilities

Capabilities and limits

What is read

  • Work items of the linked project: summary, description, status, issue type and last update
  • Acceptance criteria from an "Acceptance criteria" section in the description
  • On demand: the current issue, recent comments, available transitions and JQL search inside the project
  • Board columns or workflow statuses for the rule wizard

What is produced

  • Requirements in the project's knowledge base
  • Refinement proposals with acceptance criteria and open questions
  • Draft test cases linked to the Jira item
  • Impact-based test runs and regression set updates

Where it can write

  • Comments: proposals, run started, run results and regression changes
  • Managed description sections after approval
  • Transitions, only to the states your rules allow
  • Defects as Jira issues when a person selects Report to… or an agent with write permission files one
  • Not written: evidence files and screenshots, or later status changes of TestingOps defects

How it connects

  • Jira Cloud: account email and API token, or Sign in with Atlassian
  • Jira Server and Data Center: personal access token
  • Optional: the TestingOps Tester Agent app for Jira Cloud, paired with a one-time setup code, or the TestingOps plugin for Jira Data Center

Account and permissions

  • TestingOps reads and writes with the permissions of the token user, the signed-in user or the app user
  • Writes need the link's "Agents may write to this tracker" switch
  • A Jira site administrator installs the app or registers the webhook address

Limits

  • 300 most recently updated items per sync; comments, attachments and custom fields are not stored
  • The knowledge copy refreshes hourly and on Sync now, not on every Jira event
  • The paired app alone cannot transition issues, look up live data for agents or read board columns; those use an API token or Atlassian sign-in
  • Impact selection needs the issue key in commit messages or branch names
  • No separate testability score: ambiguities appear as open questions
  • The app works with TestingOps cloud; the Data Center plugin supports Jira 9.12 LTS

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A team moves PAY-412, "Pay an invoice with a saved card", to Test. The Tester Agent finds two commits carrying PAY-412 in the payments repository, selects the four cases linked to the story and the three cases affected by the changed files, and runs them on RunningOps.

All seven pass, so the agent comments the counts with a link to the run and moves the item to Ready for release, a transition the team's rules allow. The passing cases join the regression plan once the change is merged.

Frequently asked questions

How can I generate test cases from Jira acceptance criteria?

Write the criteria in an Acceptance criteria section of the description, or let the Tester Agent propose them. Once they are approved, the agent writes draft test cases so that every criterion is checked by at least one case, and links them to the Jira item for review.

Can AI test agents take part in a Jira workflow?

Yes. Board rules attach agent actions to board columns or workflow statuses: refine, write acceptance criteria, write tests, analyse impact, run tests, update the regression set and comment. Each rule runs in suggest, approve or autonomous mode, and autonomous rules must list the transitions they may make.

How can Jira requirements inform regression testing?

When an item reaches your test column, the agent selects cases linked to the requirement and cases affected by commits that carry the issue key, runs them, and adds passing cases to a regression plan once the change is merged.

Does TestingOps keep a copy of all our Jira issues?

It keeps the items of the projects you link, read with the permissions of the connecting user. Each sync takes the 300 most recently updated items, optionally narrowed by JQL inside the project, hourly and on Sync now. Comments, attachments and custom fields are not stored.

Do we still need an API token if we install the Jira app?

The app covers events, comments and knowledge sync without a token. Transitions, live lookups by agents and board columns still use an API token or Atlassian sign-in.

What does TestingOps write back to Jira?

Comments with run results and a link to the run, managed description sections you approved, and transitions your rules allow. Evidence files stay in TestingOps; defects are created in Jira when someone selects Report to… or an agent with write permission files one.

Does it work with Jira Data Center?

Yes, with a personal access token. The TestingOps plugin for Jira Data Center (Jira 9.12 LTS) adds Jira events and comments as a service user.

Next step

See the Tester Agent work on one of your Jira projects: request a demo and bring a story that is ready for testing.

Request a demoMore project tools integrations