Jira integration

Jira test management integration with two-way bug sync

Keep Jira as the place work is planned, and TestPlum as the place it is tested. Bugs move between the two, stories become requirements, and each story shows the tests that cover it.

By the TestPlum teamChecked

Short answer

TestPlum connects to a Jira project with an account email and API token. Bugs sent to Jira stay in sync both ways: closing the issue resolves the bug, and resolving the bug closes the issue. Jira stories import as requirements by JQL, follow their story, and get one comment with their test coverage.

What the Jira integration does

  • Send a bug to Jira. From a bug in TestPlum, create the issue in Jira. The two stay linked.
  • Two-way bug state. Move the Jira issue to a status in the done category and the TestPlum bug is resolved as fixed. Reopen it and the bug goes back to New. Resolve, close or reopen the bug in TestPlum and the issue follows, through your Jira workflow's transitions.
  • Jira stories as requirements. Import stories with a JQL query. Each becomes a requirement keyed by its Jira key, with its title, description and status.
  • Coverage on the story. TestPlum keeps one comment on each imported story: how many tests cover it, how many pass, fail or have not run, and a link back. The comment is edited in place when coverage changes.
  • Xray import. Teams moving from Xray can import tests from Xray JSON or CSV, including Jira's CSV export.

Set it up

  1. Add the connection. An organization admin adds a Jira connection: the site address, the Jira project key, the account email and an API token for that account.
  2. Send a bug. Open a bug in TestPlum and send it to the Jira connection. The bug shows the linked issue, its state and when it last synced.
  3. Import stories. On Requirements, import from Jira with a JQL query, for example the stories in the current version. Importing again updates the same requirements.
  4. Add a webhook (optional). An admin can create a webhook for the connection. TestPlum shows its URL and secret once; add them in Jira so changes sync at once.

How sync stays correct

TestPlum remembers the last state both sides agreed on. That lets it tell a real change in Jira from the echo of its own change. If both sides moved since the last sync, TestPlum's change wins.

Without a webhook, TestPlum pushes its own changes to Jira within seconds and reads back every linked item every five minutes. With a webhook, a change in Jira triggers a sync at once. TestPlum only reads the issue key from the webhook and then fetches the state from Jira itself, and it rejects any webhook call whose signature does not match the secret.

Every bug and requirement page shows the last sync and any error, with a Sync now button. The connection list shows how many items are linked and when it last synced.

When Jira's workflow does not fit

Jira moves an issue only through the transitions its workflow allows. To close an issue, TestPlum uses the first transition into a done status. To reopen one, it uses the first transition to a new status, or to an in-progress status if there is none. When no transition fits, the sync stops with a clear error on the bug, so nothing changes silently.

Requirements, coverage and the release verdict

Imported stories are requirements like any other. Link tests to them, run the tests, and the requirement shows whether it is verified. Requirements verified is one of the checks behind the release verdict, so a story with failing tests keeps the release at Not ready, with that reason in plain words.

Open critical bugs are another check. When a sent bug is closed in Jira, it is resolved in TestPlum, and the verdict updates on its own.

Limits

  • One story import takes up to 500 stories. The import tells you when there were more.
  • A bug can be sent once. Sending it again is refused, because it is already linked.
  • Removing a connection keeps the links on bugs and requirements; they just stop syncing.
  • TestPlum does not charge for Jira users. It is priced per tester; see pricing.

Frequently asked questions

Is the Jira sync really two-way?

Yes, for bug state. Closing or reopening the Jira issue changes the TestPlum bug, and resolving, closing or reopening the bug changes the Jira issue.

Do I need a webhook?

No. Without one, TestPlum reads every linked item back from Jira every five minutes. A webhook makes Jira's changes arrive at once.

What happens if someone deletes the coverage comment on a story?

TestPlum writes it again on the next sync. It keeps exactly one comment per story and edits it when the text changes.

Can I import Jira stories as requirements?

Yes, by JQL, up to 500 stories per import. Each is keyed by its Jira key, so importing again updates instead of duplicating.

Does TestPlum work with GitHub Issues too?

Yes. Bugs can be sent to GitHub Issues with the same two-way state sync. Story import as requirements is Jira only.

Do people in Jira need a TestPlum seat?

No. TestPlum charges per tester and never for people in connected tools such as Jira.

Jira is a trademark of its owner. TestPlum is not affiliated with or endorsed by it.

Find out whether your next release is ready

Create a workspace, import your tests or write a few, and record a run. Everything on this site is in the product today.