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
  • Pre-filled action sequences
  • Extending pre-filled action sequences

Was this helpful?

  1. From TOPdesk to Jira

Action sequences

PreviousTransition Change/IncidentNextCreate/update Jira issue

Last updated 1 year ago

Was this helpful?

The TOPdesk Jira Integration makes it possible to create or update a Jira issue based on activity in TOPdesk. We use TOPdesk's action sequences to make that happen. A Jira administrator can download pre-filled action sequences in the Jira app. A TOPdesk operator can import these action sequences in TOPdesk.

On the 7 of March 2023 TOPdesk have released a detailing visual changes to the Action Sequences. This documentation has been updated to reflect these changes to the best extend possible.

Pre-filled action sequences

The Jira TOPdesk integration allows you to download pre-filled action sequences to make it easier to configure your automation process. A Jira admin can configure and download these action sequences in Jira. A TOPdesk operator can then import these in TOPdesk.

Action sequences are only downloadable once for the following reason:

The action sequence generates an authentication key that is not saved on our servers. Because the key is not saved somewhere, a new key is generated each time an action sequence is created.

Extending pre-filled action sequences

Extending pre-filled action sequences require a deep understanding of Jira's issue, fields and workflows. We recommend that only Jira admins and TOPdesk operators perform these modifications.

Pre-filled action sequences can be modified in TOPdesk or a JSON editor. By default only some fields are copied from the TOPdesk change or incident to the Jira issue.

To get familiar with modifying action sequences we provide a few blueprints with differing functionalities.

blog post
Create/update Jira issue
Configure action sequences