Automatically create issues in Jira Service Management when Cloudmon alarms fire, and optionally resolve them when the alarm clears.
The Jira Service Management integration allows Cloudmon to create issues in a project on your Jira Cloud site when an alarm fires. If automatic resolution is enabled, Cloudmon also moves the issue to its resolved status when the alarm clears, so your team can track and resolve alarms through your existing workflow.
Collect the following details in Jira before you configure the integration in Cloudmon.
| Field | Description |
| Site URL | Your Jira site address from the browser address bar, for example https://acme.atlassian.net. |
| API Token | Created from your Atlassian account. See Manage API tokens for your Atlassian account. |
| Project Key | The short key of the target project. See Edit a space's details. |
| Issue Type | One of the types configured for that project, for example Task or Incident. See What are work types?. |
| Resolution Transition | The workflow transition that moves an issue to its resolved or done status. See Configure advanced work item workflows. |
The API token is stored encrypted and is never shown again after saving. Use Test Connection to verify the site, account and project before saving.
Jira Account
| Field | Description |
| Integration Name | A display name to identify this integration in Cloudmon, such as "Ops Jira". |
| Site URL | The URL of your Jira site, for example https://acme.atlassian.net. |
| Account Email | The email address of the Jira account that owns the API token. |
| API Token | The API token created in Jira. |
| Project Key | Enter the Site URL, Account Email and API Token first, then click Fetch Projects. Then select the project from the dropdown. |
| Issue Type | Select a project first, then select an issue type from the dropdown. Use the Refresh button to reload the issue types for the selected project. |
| Resolution Transition | The name of the workflow transition that moves the issue to its resolved status. The default is Resolve. |
Ticket Settings
| Field | Description |
| Ticket Subject | The text used as the Jira issue subject. The default is $device_name is $severity - $title. Type $ to pick a replaceable tag from the list, and use the reset icon beside the field to restore the default. |
| Create Tickets For Severities | Select the alarm severities that create a Jira issue: Down, Critical, Trouble and Attention. At least one must be selected. |
| Resolve Ticket Automatically When Alarm Clears | Enabled by default. When enabled, Cloudmon resolves the Jira issue when the alarm clears. When disabled, the Jira issue must be resolved manually. |
| Ticket Tags | Optional. Type a tag and press Enter to add it. Add as many as you need. |
The Reset button restores the form to its default values, and Close exits without saving.
When this alarm fires, Cloudmon creates an issue in Jira automatically, for the severities selected in the integration.