Jira Cloud integration
Raise and link Jira tickets from an asset page, and keep the service desk history next to the asset it is about.
What it does
Every asset page has a Tickets card. With a Jira Cloud site connected, Raise Jira
ticket opens a form with the summary and description already filled in from the
asset: tag, name, hardware, serial number, assignee, location and a link back to the
asset page. Edit either field, raise it, and the new issue is created in your
configured project and linked to the asset. Link ticket accepts an issue key such as
HELP-123 or a Jira URL. The card lists each linked ticket with its key,
summary and status, newest first.
- Statuses are cached and refreshed with Refresh status; the asset page never waits on Jira
- The daily renewals digest can raise one Jira ticket per digest with the same items, switched on in the Alerts tab
- Ticket links appear in the asset's history and in the organisation data export
- The iOS app shows linked tickets on the asset screen and can raise a Jira ticket the same way
- An optional API token expiry date, warned 30, 7 and 1 days ahead by the digest
- Verified against a live Jira Cloud site
Day-to-day use and the error messages are covered in the ticketing documentation; the digest itself is in reports and alerts.
What it needs
A Jira Cloud site, an API token and a Team licence.
A Team licence
Ticketing is included in every Team tier; see the pricing page. Linking a ticket by URL works without it.
A Jira Cloud site and an account
An account that can create issues in the project you choose. A dedicated service account is better than a personal one: tickets raised from Tagaris are attributed to it, and it survives staff changes.
An API token
Signed in as that account, create a token at id.atlassian.com under Security, then API tokens. Atlassian shows it once.
The Jira card
Settings, Integrations, then Jira (administrators only): site URL, account email, API token, the project key for new tickets and the issue type (Task if left blank). Test connection signs in and checks the project exists, so a green result means raising tickets will work.
Link any ticket by URL (free)
Without the integration, and on the free tier, the Tickets card still takes a URL from any service desk: Halo, ServiceNow, Zendesk, Jira or anything else, with an optional label. The link opens the ticket in the other system. No setup and no licence. The Jira integration adds what a URL cannot give you: raising a ticket with the asset details filled in, linking by issue key, and the cached status on the asset.
What it will not do
- Change a ticket. Tagaris only creates issues and reads their summary and status. It never transitions, comments on, edits or deletes one.
- Touch Jira when you unlink. Unlinking a ticket in Tagaris leaves the ticket itself as it was. Jira stays the system of record.
- Show live status. The card shows the state as of the last refresh.
- Raise a ticket per item from the digest. It is one ticket per digest run.
- Connect to anything other than Jira Cloud. It signs in to a site at atlassian.net with an Atlassian API token.
Everything else that connects to the register is on the integrations page; the asset page itself is shown on the features page.
Common questions
Which Jira does it work with?
Jira Cloud, a site at atlassian.net, signed in with an Atlassian account email and API token.
Can I link tickets from Halo, ServiceNow or Zendesk?
Yes, by URL, on the free tier with no setup. The Jira integration adds raising tickets with the asset details filled in, linking by issue key and the cached status.
Why does a ticket's status look out of date?
Statuses are cached rather than read live. Use Refresh status on the Tickets card to re-read the summary and status of the asset's Jira tickets.
Raising a ticket fails with a 400 from Jira. What is wrong?
Usually the issue type does not exist in that project; many Jira service desk projects have no Task type. Set an issue type the project accepts, for example one from its board.
Keep tickets next to the kit they are about
The live demo shows the Tickets card on an asset page. Jira ticketing is included in every Team plan.