Connect Jira
Connecting Jira Cloud puts Declara's work where your engineers already plan theirs. An alert that needs assessing, or a case that opens, becomes an issue in the project you choose. Everything that happens to a case afterwards (a stage filed, a deadline overdue, the case closed) is added as a comment on that same issue.
Jira is on the plans that include integrations.
Before you start
- A Jira Cloud site, such as
https://your-company.atlassian.net. Jira Data Center and Server are not supported. - A project to file into, and its key, such as
SEC. - An Atlassian API token for the account the issues should be created by. Create one at id.atlassian.com. The account needs permission to create issues and add comments in that project.
Connect it
- Open Settings → Integrations and choose Jira Cloud.
- Enter the site, the project key, the issue type (Task by default), the account email and the API token.
- Press Connect, then Test to open a test issue.
The token is encrypted before it is stored and is never shown again. To change it, remove the connection and add it again.
What it sends
The same thing Slack gets: a title, a sentence, and a link back to Declara. Never your
component inventory and never a report packet. Issues are labelled declara, plus the
event, such as alert-created.
A delivery that fails (Jira down, a rate limit) is retried for about ten hours, like every other integration, and a retry never opens a second issue for the same alert or case. The events it can receive are listed in the event catalog.