Jira two-way integration: link assets to tickets

SimpleAMS integrates with Jira Cloud in both directions:

• Outbound: a button on every asset creates or links a Jira issue; asset events (check-out, status change) post comments back to Jira.
• Inbound: a Jira webhook mirrors issue updates into the asset's timeline so you don't need to flip tabs.

1. Generate a Jira API token

1. Sign in at id.atlassian.com.
2. Security → API tokens → Create API token.
3. Label: "SimpleAMS". Copy the token.

2. Configure in SimpleAMS

1. Go to Settings → Integrations → Jira (Cloud).
2. Fill:
   • Jira Cloud subdomain: just "acme" for acme.atlassian.net, no protocol.
   • Account email: the email of the user that owns the token.
   • API token: from step 1.
   • Default project key: e.g. OPS. Used when you create an issue without picking one.
3. Tick Enable this integration and save. SimpleAMS generates a webhook secret at this point.

3. Set up the webhook in Jira

Copy the Webhook URL shown on the integration card (it includes the secret).

1. In Jira, click the cog → System → Webhooks → Create a webhook.
2. Name: "SimpleAMS asset link".
3. URL: paste the webhook URL.
4. Events: tick Issue created, Issue updated, and Issue deleted.
5. Save.

4. Daily usage

• From an asset: click Create Jira issue. SimpleAMS opens an inline form, you pick project + summary, we POST to Jira and link the response back.
• Link an existing ticket: paste the issue key (e.g. OPS-1234) into the same form.
• Asset events posted to Jira: when you check the asset out, change its status, or log maintenance, SimpleAMS adds a comment to the linked Jira issue with the change.
• Jira changes mirror to SimpleAMS: closing the ticket in Jira marks the asset link as resolved; reopening reopens it.

5. Notes

• Jira is a Business-plan integration.
• The webhook secret is part of the URL - if it leaks, regenerate it by toggling the integration off and back on.
• Jira Server / Data Center isn't supported - this guide is for Atlassian Cloud only.