Skip to content
Help Center
Submit a request Sign in

Tags

Configure Jira case integration

Updated Wednesday, October 28, 2026 · Marc Staine

Jira integration connects support cases with engineering work and controls the updates returned to agents. Use the setup checklist and activity/status policies to make automatic changes predictable.

Applies to: Supportbench Core. Location: Settings → Integrations → JIRA. Access and available controls depend on your role and account capabilities.

Before you begin

  • Confirm you can administer integrations and have access to the intended provider workspace.
  • Record the existing connection and routing choices. Use a representative test record before enabling broad synchronization.
  • Obtain credentials through your approved provider process; do not place secrets in articles, screenshots or support messages.

Configure and verify

  1. Open this integration from Settings → Integrations.
  2. Review the connection identity and enter only the provider details requested by the page.
  3. Choose the available synchronization, routing or activity options described below.
  4. Save settings and use the displayed verification action when available.
  5. Inspect one representative record on both sides and review the integration status before relying on automated processing.

Settings reference

Connection and operating controls

SettingWhat it controlsHow to choose
Jira hostnameThe Jira instance to connect.Use the exact intended Cloud or Data Center hostname.
Username / Password or API tokenJira credentials; stored credential state and a reveal control are shown.Cloud uses the Atlassian email/API-token pattern shown by setup guidance; use the compatible account method for Data Center.
Automatic Jira activitiesAll changes, comments and status, new comments, status only, or none.Choose the update volume that agents need.
ActiveControls integration availability.Review the webhook separately when disabling Jira updates.
Setup checklist / Retry setupTracks the add-on, webhook and Cases custom field.Resolve incomplete setup items and recheck them.
Webhook URL / CopyDisplays the configured inbound update destination.Use the displayed destination when following setup guidance.
Issue key / Test connectionTests access using a representative issue.Use a non-sensitive issue accessible to the intended integration identity.
Remove JiraRemoves the configured integration.Review linked-case and provider-webhook dependencies first.

Case update policy

SettingWhat it controlsHow to choose
Activity customizationPresets and detailed choices determine which incoming updates become case activity.Choose a readable signal level and verify with future deliveries.
Jira → Supportbench status mappingsOptional mappings from Jira status to case state.Review every transition, especially closure and reopening, before enabling automation.

Build a status mapping

Select Add mapping. New mappings start Off. In When · Jira, choose the Jira project and the status it changes to. In Then · Supportbench, choose the case status to set. These pickers support search.

Under Only when the case is, select one or more current case statuses. Selected chips show a checkmark; click a chip or focus it and press Space to change the selection. The summary describes the transition. Closing a case requires every linked Jira issue to be Done. Selecting Closed as an eligible current status can allow a mapping to reopen cases.

Turn the mapping On and select Save Changes when it is ready. Removing a mapping also takes effect only after saving. You can save up to 50 mappings. Every row, including an Off row, must be complete or removed. Enabled mappings cannot overlap for the same Jira project, Jira status and eligible current case status.

Choices load automatically for existing mappings and when adding the first mapping. Refresh choices reloads projects and case statuses without saving changes. Use Retry statuses if a project's status lookup fails. Saved selections are retained if a lookup fails or an option is unavailable; review values labeled Saved selection before enabling a mapping. A failed save retains your edits for correction and retry.

Behavior to know

  • Custom activity policies affect future deliveries.
  • Automatic closure requires every linked Jira issue to be Done. Review Closed/reopen mappings deliberately.
  • An interrupted status action blocks later automatic changes. Turning Active off does not remove the provider webhook; existing webhook deliveries can continue until the webhook is removed in Jira.

Recommended use

  • Enable only the flows your support process needs and identify an owner for connection failures.
  • Test mappings and routing with representative records before broad use. Review existing data before a resynchronization or removal.

Worked example

  1. Configure the Jira connection and test a representative issue.
  2. Complete the setup checklist.
  3. Choose the activity policy and any status mappings.
  4. Link a test case and inspect a future Jira update before broad use.

Troubleshooting

ProblemWhat to check
The item is missing from a picker.Check Active, division access, parent hierarchy, enabled modules, and the user’s role. Reopen the consuming form after saving.
The form rejects a save.Read the displayed validation message. Check required values, text limits and permitted scope; do not change unrelated settings to bypass validation.
An existing record still shows an old value.A configuration change and a record change are different operations. Inspect the record and relevant references before assuming the save failed.
  • Integrations → Use the data synchronization log
  • Organization → Configure agent roles and division access

For additional setup and usage context, see these related guides:

Was this article helpful?