Skip to content
RecipesDoc

Mention @Certyn on a Jira or Linear Issue, Ask About the Bug, Start a Retest

Developers ask Certyn inside the issue they work on and get the answer in the issue thread. What works there, and what needs the web app.

For teams whose developers live in Jira Cloud or Linear.

Your setup

  • Your team tracks work in Jira Cloud or Linear.
  • Certyn files bugs there, or you link Certyn issues to tickets.
  • Developers want to ask is this fixed? and start a retest from the ticket.

Say this to Certyn

In the web chat, once:

Connect Linear so the team can mention @Certyn on issues.

Then on an issue:

@Certyn the fix is on staging. Retest the linked bug and tell me what the last run found.

What Certyn does

Setup, once:

  1. Linear: opens the Linear connect form. Connect Linear workspace adds Certyn as an app user, bound to the chat's project and environment. A Linear workspace admin must do it.
  2. Jira Cloud: a Jira site admin installs the Certyn app, then opens Apps → Certyn → Connect to Certyn and approves the site in Certyn with a project and environment. An Atlassian org admin creates a free service account named Certyn (Directory → Service accounts). People mention that account. It needs no token and no Jira seat.

On the issue:

  1. In Jira, Certyn replies looking into this, then edits that reply into the answer. In Linear, a mention or delegating the issue to Certyn opens an agent session, and the answer shows in the thread.
  2. Certyn finds the Certyn issue linked to the ticket. It can:
    • say what runs found, the last retest and its result, and which tests cover it;
    • start a retest or a run, after asking (answer with another mention);
    • search issues and test cases, and read the wiki.
  3. Each ticket keeps one conversation, so a later mention keeps the context.

What you get

  • Answers in the issue thread, with links to Certyn runs and issues.
  • Retests started from the ticket. The result lands on the Certyn issue.

Limits

  • No forms or approval prompts there. Secrets, sign-ins, connections, variables, environments, schedules and other settings are refused. Do them in the web chat.
  • No Machine there. Certyn starts a run and links it; mention it again later for the result.
  • A retest needs a confirmed Certyn issue linked to the ticket or to a test case.
  • One Certyn project and environment per Jira site or Linear workspace.
  • Jira Cloud only. The Jira app is installed from a link the Certyn team sends you; ask support for it.