For teams that track work in Jira and want Certyn's bugs there, not in a second list.
Your setup
- Jira Cloud with one or more Jira projects.
- Certyn already tests your staging environment.
- You want Certyn to check each fix again.
Say this to Certyn
Connect our Jira and file the bugs you find in the SHOP project. When a fix is deployed, retest it.
What Certyn does
- Opens the Jira connect form. A Jira site admin installs the Certyn app, then opens Apps → Certyn → Connect to Certyn in Jira and approves. Or you enter an API token: base URL, user email and token.
- If the site has more than one project, asks which one gets the issues and saves it as the default (
tracker.target.set). - For each real product bug, asks before it files it in Jira (
tracker.issue.create), then links the Certyn issue to it. To use a Jira issue you already have, it links that one instead (tracker.issue.link). - After the fix is deployed, you say retest issue 12 in the chat, or write @Certyn retest this on the Jira issue. Certyn runs the bug again on the environment where it was found.
What you get
- One Jira issue per bug, with the write-up from the run. Ten failing tests on one broken page make one issue.
- The Certyn issue keeps the screenshots and the session, and shows the Jira link.
- The retest result (passed or still failing) on the same Certyn issue, with the new run's evidence.
- The Jira status when you ask: what is the Jira status of issue 12?
Limits
- Certyn asks before it creates each Jira issue. It does not file every finding on its own. Say file it in Jira when you agree.
- Retest needs a confirmed issue that is linked to a Jira issue or a test case.
- A passing retest does not close the Jira issue. Close it yourself, or ask Certyn to add a comment.