Devolutions ForumDevolutions Forum

Ticketing Service: Jira Integration

Ticketing Service: Jira Integration

avatar
Jimmy P

Hi Team,

We are attempting to configure Jira integration in Devolutions Server / RDM against our Jira Data Center instance.

It appears the integration is calling the Jira Cloud API path (/rest/api/3/) instead of the Jira Data Center API path (/rest/api/2/).

Questions:

  1. Does the current Jira connector support Jira Data Center?
  2. Is there a configuration option to force API v2 instead of v3?


Any guidance on the correct configuration for Jira Data Center environments would be appreciated.

Thank you!

All Comments (1)

avatar
Patrick Ouimet

Hello Jimmy,

Thank you for reaching out to the Devolutions support team.

Based on our current documentation, the Ticketing service “Jira integration” is configured using an Atlassian account API token and an Atlassian Cloud-style server URL (example: https://yourorganization.atlassian.net/). In that mode, Jira REST v3 endpoints (/rest/api/3/) are expected, and there is no setting in the Ticketing service configuration to force REST v2 (/rest/api/2/).

Since you are targeting Jira Data Center, please share the following so we can confirm compatibility in your specific setup and advise next steps:

  • Remote Desktop Manager version/build
  • Devolutions Server version/build
  • Jira Data Center version
  • The Ticketing server URI currently configured
  • The relevant RDM logs showing the Jira call/response when refreshing filters or selecting a ticket (sanitize any sensitive data)


If Jira Data Center (REST v2) support is required and not currently available in this connector, this can also be opened/considered as a feature request thread for the product team to review.
Documentation:


Best regards,

Patrick Ouimet