Skip to content

Link Jira tickets to vScope assets

Add a link to the vScope asset page on every new Jira Service Management (JSM) ticket that references an asset. Agents can open the asset in vScope from the ticket.

  • Assets imported from vScope with the UUID attribute, as described in Sync vScope assets to Jira Service Management Assets.
  • A ticket field of type Assets objects that references the imported object type. The field is filled in when the ticket is created.
  • Jira administrator permission to create Global automation rules.
  1. In Jira, go to Settings > Work items > Custom fields and open your Assets field.
  2. Note the field ID from the address bar, for example customfield_10462.
  1. Go to Settings > System > Global automation > Create rule.

  2. Set the trigger to Work item created.

  3. Add a Work item matches JQL condition so that the rule only runs on tickets that have the field filled in:

    project = {PROJECT_KEY} AND cf[{FIELD_NUMBER}] IS NOT EMPTY

    {FIELD_NUMBER} is the number in the field ID, for example 10462 in customfield_10462.

  4. Add a Comment on work item action. Select Internal if the project offers it, and enter:

    vScope: https://{VSCOPE_HOST}/ui/properties/{{issue.customfield_{FIELD_NUMBER}.uuid}}/about

    Replace {VSCOPE_HOST} with your vScope address and {FIELD_NUMBER} with the number from the previous step. Keep uuid in lowercase.

  5. Turn on Prevent duplicate comments and publish the rule.

  1. Create a ticket and select an asset in the Assets field.
  2. Open the ticket and confirm that it has a comment with a vScope link.
  3. Click the link. The About page of the asset opens in vScope.

If the link is incomplete or doesn’t open, see the next section.

  • The comment contains the text {{issue...}}: The smart value doesn’t resolve. Use the field ID (customfield_...), not the field name.
  • The link ends with /properties//about: The smart value is empty. Use the attribute’s internal name in lowercase (uuid), and confirm that the object has a value in its UUID attribute.
  • vScope shows “Page not found”: The asset no longer exists in vScope, or its UUID has changed. Open the object in Assets and compare its UUID with the UUID column in the vScope table.
  • The rule doesn’t run: Check that the rule is enabled and that the audit log shows the trigger. A ticket without a value in the Assets field doesn’t match the JQL condition.
  • Agents can’t see the comment: On JSM, a comment is visible to the customer unless it is internal. Select Internal in the comment action.

For other ways to open vScope from Jira, such as a URL attribute on the object, see the Optional: link back to vScope section in Sync vScope assets to Jira Service Management Assets.