EvalSuite for Jira Cloud: Connect, Use, and Remove

Before you start

EvalSuite keeps the coaching workflow and canonical action-item history inside EvalSuite. Jira is the linked execution system for teams that already run work there.

The shipped sync is org-scoped and limited to persisted action items. Accepted AI follow-up drafts only become ticket-eligible after they are saved into `action_items`.

• EvalSuite syncs title, generated EvalSuite context body, assignee, due date, and open/completed state.
• Ticket creation is always explicit. EvalSuite does not silently export AI drafts or notes into Jira.
• Remote delete never deletes the EvalSuite action item. The link moves to `Needs attention` instead.
• If an action-item owner has no Jira member mapping, the Jira issue is created or updated unassigned and the link shows `Needs mapping`.

Connect the app

Use the connection flow when your workspace is ready to authorize EvalSuite against one Jira Cloud site.

1. Open `Settings -> Integrations -> Jira Cloud` in EvalSuite.
2. Click `Connect Jira Cloud`.
3. Complete the Jira OAuth flow for the Jira site you want EvalSuite to use.
4. Return to EvalSuite and confirm the workspace connection shows as `Connected`.

Configure org destinations

Destinations tell EvalSuite which Jira project and issue type to use for newly created tickets.

• EvalSuite shows the project workflow statuses to help you validate the workflow shape, but the actual done/reopen automation still uses the transition IDs you save here.
• If no active destination exists, `Create Jira ticket` is blocked until an admin or manager saves one.

1. In `Settings -> Integrations -> Jira Cloud`, open the `Destinations` section.
2. Choose the Jira project and issue type that should receive EvalSuite action items.
3. Enter the Jira transition ID your workflow uses to move an issue to done.
4. Enter the Jira transition ID your workflow uses to reopen an issue.
5. Mark one destination as the default if you want managers to create Jira tickets without picking a destination each time.

Configure member mappings

Member mappings link EvalSuite `profiles.id` to Jira accounts so assignee sync stays org-safe and deterministic.

• If a Jira assignee changes to an unmapped Jira user, EvalSuite keeps the local owner unchanged and surfaces `Needs mapping`.
• If the EvalSuite owner has no Jira mapping, Jira stays unassigned remotely instead of blocking ticket creation.

1. Click `Auto-match by email` first. EvalSuite checks active org members against Jira users and saves exact matches.
2. Review the saved mappings list.
3. Add a manual mapping when the Jira account does not share the same email as the EvalSuite member.

Create a Jira ticket from an action item

Use this when the commitment is already real and you want the work represented in Jira immediately.

1. Open the action item in EvalSuite.
2. Click `Create` in the Jira controls.
3. EvalSuite creates the Jira issue in the default Jira destination, stores the durable link, and adds a backlink to the EvalSuite action item.

Link an existing Jira issue

Use this when the work already exists in Jira and you want EvalSuite to stay aligned with it.

1. Open the action item in EvalSuite.
2. Click `Link existing` in the Jira controls.
3. Paste a Jira issue key or Jira issue URL.
4. Confirm the link. EvalSuite fetches the remote issue and stores the durable Jira link.

Understand sync behavior and conflict handling

EvalSuite and Jira use field-level last-writer-wins by `updated_at` timestamp for supported fields.

• Remote reopen always wins. If the Jira issue is reopened, EvalSuite clears `completed_at` and the action item reappears in carry-forward.
• Remote done marks the EvalSuite action item complete when Jira closes the issue and EvalSuite is still open.
• If both sides mark done in the same webhook window, the result is idempotent because both sides agree.
• If both sides edit the title in the same sync window, the newer timestamp wins and overwrites the older value.
• Remote due-date removal clears the local due date when Jira is newer.
• Remote delete or archive never deletes the EvalSuite action item. The link moves to `Needs attention` for manual repair.

Troubleshooting

Use Support when the Jira connection is blocked, token refresh fails, or the workspace needs manual diagnosis.

• `Needs mapping` means the local owner or remote assignee is not fully mapped yet.
• `Needs attention` means the Jira issue was removed, archived, or otherwise stopped behaving like a durable sync target.
• `Paused` usually means the Jira token was revoked or the provider was disabled for the workspace.
• `Queued syncs` in the Jira settings card means EvalSuite has replayable work waiting for the next usable Jira connection.

Remove access cleanly

Use this when your workspace no longer wants Jira-backed action-item sync.

• Existing EvalSuite action items remain in EvalSuite after removal.
• Linked Jira rows move to `Paused` or `Needs attention` based on the last known state. EvalSuite does not delete historical coaching artifacts.

1. Open `Settings -> Integrations -> Jira Cloud` in EvalSuite.
2. Click `Remove`.
3. Confirm the connection is no longer active.

Sources and verification basis

• Atlassian OAuth 2.0 (3LO) apps
• Atlassian Jira Cloud webhooks
• Atlassian Jira REST webhooks API

Need Jira setup help?

Use Support if Jira authorization, destination setup, or member mappings need manual verification before your workspace can rely on synced action items.

Open Support · Create workspace