Jira Service Management
Connect NetLock RMM to Jira Service Management Cloud: alerts become requests of a chosen request type, the all-clear adds an internal comment and moves the request to a chosen status.
Jira Service Management
Requirements
- A Jira Service Management Cloud site, reached at
https://<site>.atlassian.net. Other addresses are refused. - An Atlassian account with an agent license that may create requests, add internal comments and transition issues.
- An API token of this account, created at
id.atlassian.comunderSecurity,API tokens. These tokens have an expiry date.
Setup
- In
Settings → Integrations, open the Jira Service Management tile and chooseConnect. - Enter the
Instance address, theAccount e-mail addressand theAPI token. - Under options, choose the
Status when closing: the done status a request moves to. If the workflow requires a resolution for that step, also choose aResolution. - Map each tenant to a request type. The list shows every service desk with its request types, so tenants can be assigned to different service desks. Tenants without a mapping are not included. Severities can be mapped to Jira priorities; that only works if the field
Priorityis on the request type. - Activate the connection.
What goes to the vendor
For every alert that passes the filter of the connection: a title, the severity, tenant, location and device name, the source, first and last time seen, the alert text, and a link to the web console if the public console URL is set. Check that this matches your data processing agreements before you activate the connection.
What happens to a ticket
- An alert becomes a request of the mapped request type. The summary ends in
[NetLock-Alert-<id>], which NetLock uses to find the request again. - When the alert ends, the request gets an internal comment. If nobody is assigned, it moves to the chosen status through the workflow transition that leads there.
- NetLock does not guess a transition. If the workflow has no transition from the current status into the chosen one, the request stays open with its comment and the history shows
no_transition.
The behaviour is set in the Settings tab, see A.14.4. NetLock never closes a ticket whose status somebody changed in the meantime, and it never deletes anything at the vendor.
Known limits
- NetLock does not fill other required fields of a request type, so a request type with such fields refuses the ticket. Use a request type that needs only summary and description.
- If a transition requires a resolution and none is chosen, or Jira refuses the transition for another reason, the request stays open and the history shows
close_refused. - Organizations are not set on a request, and there is no company import. The tenant is named in the text of the request.
- Assets are not part of this integration.
Related
Zammad
Connect NetLock RMM to Zammad: alerts become tickets in a group, the all-clear adds an internal note and closes the ticket, organizations can be imported as tenants.
Freshservice
Connect NetLock RMM to Freshservice: alerts become tickets, the all-clear adds a private note and sets a status, devices can optionally be synced as assets.