Jira Cloud

Creates a Jira issue for a ticket and keeps the two sides in step: ticket comments and state changes go to the issue, Jira comments and status changes come back to the ticket. The issue key is shown on the ticket under the Links tab.

Setup

1. In Jira, create an API token for the account that should create issues (Atlassian account → Security → API tokens).
2. In Stoneity open Settings → Apps → Marketplace → Jira Cloud → Install and fill in:
   • Site URL — e.g. https://acme.atlassian.net
   • E-mail and API token of the Jira user
   • Project key — e.g. SUP
   • Issue type — e.g. Task
   • Events and optional boards
3. Save. Stoneity calls GET /rest/api/3/myself to verify the credentials before the installation is activated.
4. Click Test under Installed apps to check the connection.

Bringing Jira changes back

1. Copy the inbound address from Installed apps → Jira Cloud → Settings.
2. In Jira go to Settings → System → Webhooks → Create a WebHook, paste the address and select the events Comment: created, Issue: updated and Issue: deleted. A JQL filter such as project = SUP keeps the traffic down.

Assignee and priority

Two optional settings mirror more than comments and status:

• Mirror the Jira assignee matches the Jira user by e-mail address. Jira privacy settings can hide the address; when that happens the change is skipped and the reason appears in the delivery log, so nothing fails silently.

• Priority mapping takes one line per priority, Jira priority = ticket priority:

  Highest = Critical
  High = High
  Medium = Normal
  Low = Low

  The right-hand side accepts either the stored value or the label shown on the board. A Jira priority with no line is left alone. Leave the box empty to skip priority entirely.

3. Optionally set a secret in Jira and enter the same value in the installation settings. Stoneity then requires a matching X-Hub-Signature on every request.

Behaviour

Change	Result
Ticket created	POST /rest/api/3/issue — summary is [#number] title, description carries the ticket body and a link back
Ticket comment added	Comment on the linked issue
Ticket state changed	Comment on the linked issue
Jira comment added	Internal note on the ticket
Jira status changed	Internal note on the ticket, and the link shows the new status
Jira assignee changed	The ticket is assigned to the matching Stoneity user, if you enabled it
Jira priority changed	The ticket priority follows your mapping, if you set one
Jira issue moved to a Done status	Note, or resolves the ticket if you chose that
Jira issue deleted	The link is marked deleted

Once an issue exists for a ticket it is stored as an external link; further create-type events for the same ticket are skipped.

Notes

• Notes created from Jira are written by the app's own service account, and comments written by that account are never sent back to Jira, so the two systems cannot echo each other.
• Credentials are stored encrypted. Rotating the API token only requires editing the installation.
• A 4xx reply from Jira (wrong project key, missing permission) is treated as permanent and is not retried; the reason appears in the delivery log.