Jira

Connect Jira so work doesn't stop at the ticket. Turn a ticket into a test, launch runs from Jira, and send verified results back — without leaving Jira.

Connect once in Settings, and you can:

• Turn a ticket into a test — import it into the workflow builder with a suggested goal.
• Trigger runs from Jira — tag a ticket, or ask the Slack assistant to test it.
• Send results back — verdict, verified issues, and replay links, written onto the ticket.
• File defects to Jira — push a Cofactor issue back as a Jira issue.
• Look up tickets from Slack — search connected Jira tickets in assistant threads.
• Keep statuses in sync — Cofactor updates connected issues through a webhook.

01Connect Jira

You need admin access in your Cofactor organization.

1. Open Settings > Jira.
2. Connect your Jira workspace and complete the OAuth flow.
3. Confirm the connection validates, then save your Jira defaults.

Saving defaults also registers the status-sync webhook (when supported). The Status sync health indicator shows whether it's active.

Multiple properties? Set Tag-triggered ad-hoc test routing before relying on tags to launch runs, or Cofactor may skip those runs.

02Turn a Jira ticket into a test

Import a ticket into the workflow builder instead of retyping it.

1. Open the workflow builder import flow and select Jira.
2. Search by key, title, or details.
3. Select the issue to pull in its details.
4. Review the suggested goal and context, then continue into the builder.

03Launch a test from a Jira ticket

Two paths, no need to open Cofactor:

• Tag a ticket — apply your trigger tag and Cofactor launches an ad-hoc test. In a multi-property org, it runs in the property set under Tag-triggered ad-hoc test routing.
• Ask in Slack — tell the assistant to test a ticket; request, progress, and results stay in one thread.

To route tagged tickets by property: open Settings > Jira, set Tag-triggered ad-hoc test routing to the right property, save, then tag a ticket and confirm the run appears. Use this when several teams share one Jira integration.

04Send results back to Jira

When a Slack-triggered ad-hoc test tied to a ticket finishes, Cofactor writes the outcome onto the ticket. Depending on the run, it can show:

05File a Cofactor issue back to Jira

When testing surfaces a defect, create a Jira issue from the Cofactor issue to hand it to your team — keeping testing output in the Jira process you already use.

06Look up Jira tickets from Slack

Pull ticket details into a conversation without switching tools.

1. In a Slack assistant thread, ask for a ticket by key, title, or details.
2. Review the results and continue with follow-ups about status, ownership, or related work.

07Keep Jira statuses in sync

When active, Cofactor keeps connected issues updated through a webhook. If sync degrades or stops:

1. Open Settings > Jira and review Status sync health.
2. If degraded or inactive, click Repair Sync.
3. If repair doesn't work, click Re-register to recreate the webhook, then confirm it's active.

Use Repair Sync when the setup can still be fixed; use Re-register when the webhook is missing.

08Settings reference

09Troubleshooting

10Related

• Slack
• Ad-hoc testing — ticket-linked runs and writebacks
• Import Jira tickets into workflows
• Issues
• Flows