TOPdesk Jira Integration
  • TOPdesk Jira Integration
  • Before you start
  • Installation
  • Release notes
    • 18-12-2024
    • 28-09-2023
    • 07-08-2023
    • 08-11-2022
    • 17-10-2022
    • 15-09-2022
    • 27-06-2022
    • 18-05-2022
    • 19-4-2022
    • 14-12-2020
    • 02-12-2020
    • 13-11-2020
    • 27-10-2020
    • 07-09-2020
    • 19-06-2020
  • From Jira to TOPdesk
    • Post functions
    • Configure the post function
      • Create/update Change
      • Create/update Incident
      • Transition Change/Incident
  • From TOPdesk to Jira
    • Action sequences
    • Create/update Jira issue
      • From linked event
      • From context menu
    • Configure action sequences
      • Updating a field
      • Transition an issue
      • Set a priority
  • Communication
    • Comments, actions, attachments
  • Advanced
    • Additional configuration
    • Troubleshooting
  • Links
    • Atlassian Marketplace
    • Support
    • Roadmap
    • Product demo
  • Security / Privacy
    • Privacy Policy
    • Security Policy
Powered by GitBook
On this page
  • Getting Jira priority id's
  • HTTP Body
  • Mapping priorities

Was this helpful?

  1. From TOPdesk to Jira
  2. Configure action sequences

Set a priority

PreviousTransition an issueNextComments, actions, attachments

Last updated 1 month ago

Was this helpful?

Setting priority is almost the same as adding a field to the fields object.

Setting a priority makes it clear for your Jira operators which issues to handle first. Syncing the priority in TOPdesk to Jira is a great way to keep everyone on the same page.

Getting Jira priority id's

To get the ID's for the Jira priorities you can use their .

HTTP Body

In this case, the default update issue action sequences has been used that is generated for changes. In this case the priority field is added.

{
  "issue": {
    "fields": {
      "priority": { 
        "id": "1" 
      },
      "summary": "${briefdescription}",
      "description": "<#list _progresstrail.requests as request>${request.richtext!}</#list>"
    }
  },
  "change": {
    "id": "${unid}",
    "number": "${number}"
  }
}

Mapping priorities

The previous example could be a great start, but most likely you don't want to configure an action sequence per Jira priority level. It would be better to use the priority from TOPdesk and sync that to Jira. This can be done by defining a field mapping inside your action sequence.

To create this field mapping, you will have to know all the priority id's from the TOPdesk priorities and the Jira priorities. There doesn't seem to be an easy way of getting all TOPdesk priority id's so one way is to bruteforce this via an action sequence and reading the logs to see the priority id.

Once you have the required priority id's you can create a mapping like the example below.

After adding the value mapping to the action sequence you can reconfigure the body.

{
  "issue": {
    "fields": {
      "priority": { 
        "id": "${_map(priorityid, 'priority mapping')}" 
      },
      "summary": "${briefdescription}",
      "description": "<#list _progresstrail.requests as request>${request.richtext!}</#list>"
    }
  },
  "change": {
    "id": "${unid}",
    "number": "${number}"
  }
}

Now, when executing the action sequence, the priorityid from TOPdesk will be converted to a Jira priority id before the HTTP request is made.

API documentation