JIRA Action Details

The JIRA action is based on templates where each template can be preconfigured with the project, issue type, assignee, and priority. When a JIRA action is triggered, it creates a ticket with those fields in it.

There is a rate limit for the action, which is set to 100 by default. This means the JIRA action will not create more than 100 tickets a minute for an account.

This new action needs to be created similar to the rest of the actions, and associated with a health rule for all transition events of the rule (OPEN, CONTINUES, UPGRADE, DOWNGRADE, CLOSE, CANCEL).

This table describes the JIRA action and transitions.
OPEN (CRITICAL or WARNING) Health rule violation started. Creates a JIRA issue. Response of this action provides the JIRA ID which is persisted against the incident.
CONTINUES (CRITICAL or WARNING) Health rule violation continues. Fetches the JIRA issue that corresponds to the health rule / affected entity, and updates the JIRA with a comment with the latest violation summary.
UPGRADE (WARNING → CRITICAL) Health rule violation now critical. Fetches the JIRA issue that corresponds to the health rule / affected entity, and updates the JIRA with a comment with the latest violation summary. May change the priority of the issue.
DOWNGRADE (CRITICAL → WARNING) Health rule violation now warning. Fetches the JIRA issue that corresponds to the health rule / affected entity, and updates the JIRA with a comment with the latest violation summary. May change the priority of the issue.
CLOSE Health rule thresholds back within limits, incident closed. Fetches the JIRA issue that corresponds to the health rule / affected entity, and updates the JIRA with a comment.
CANCEL Health rule configuration has changed or system lifecycle (restart, entity deleted) caused incident to be cancelled. Fetches the JIRA issue that corresponds to the health rule / affected entity, and updates the JIRA with a comment.