For teams that track work in Jira, Linear or GitHub Issues, and want Certyn's bugs there, not in a second list.

Your setup

Jira Cloud, a Linear workspace, or a GitHub repository with Issues on.
Certyn already tests one of your environments.
You want real bugs in your tracker, not every failed test, and each fix checked 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.

Or: File the bugs you find in our Linear team WEB, or as GitHub issues in acme/shop.

Opens the connect form for your tracker:

Tracker	How you connect
Jira	A Jira site admin installs the Certyn app, then opens Apps → Certyn → Connect to Certyn in Jira and approves. Or enter an API token: base URL, user email and token.
Linear	Connect Linear workspace signs in once for the whole workspace. Certyn then works as its own app user. Or paste a personal API key.
GitHub Issues	Install the Certyn GitHub App and pick the repository. Or use a personal access token.

If there is more than one project, team or repository, asks which one gets the issues and saves it as the default.
For each real product bug, asks before it files it, then links the finding to the new issue. To use an issue you already have, it links that one instead.
After the fix is deployed, you say retest finding 12 in the chat. On a Jira or Linear issue you can also write @Certyn retest this (see Certyn in Jira or Linear). Certyn runs the bug again on the environment where it was found.

One issue per bug, with the write-up from the run. Ten failing tests on one broken page make one issue.
The finding keeps the screenshots and the session, and shows the tracker link.
The retest result (reproduced or not) on the same finding, with the new run's evidence.
The tracker status when you ask: what is the Jira status of finding 12?

Certyn asks before it creates each issue. It does not file every finding on its own. Say file it in Jira when you agree.
GitHub Issues has no @Certyn mention. Ask for the retest in the chat on Home.
GitLab connects for CI only. There is no GitLab issue tracker.
Retest needs a confirmed finding that is linked to a tracker issue or a test case.
A passing retest does not close the finding or the tracker issue. Close them yourself, or ask Certyn to add a comment with the result.