Link to source Ticket in Jira

[masteragi]

Hello dear Community!

First of all, let me share my appreciation for the development of this tool! 🙏

I would like to include a link to the original Jira ticket in the migrated Azure DevOps tickets (perhaps just as the last comment in the history). Is there a simple way how I can achieve this using the configuration? I haven't found it in the documentation that is why I am asking here... If it's not supported yet, I can add an additional mapper that concatenates a base url (provided in the config file) and the Jira Issue Key.

Thanks a lot in advance for any ideas.

[Alexander-Hjelm]

Hello @masteragi!

We usually facilitate this by creating a custom text field in the Azure DevOps process, and mapping the issue key there, like this:

      {
        "source": "key",
        "target": "Custom.JiraReference"
      },

Then the JiraReference field in ADO will end up holding the jira issue key (Project Key + issue number).

We do not support mapping the full URL of the issue. Therefore I have labeled this issue as a feature request.

I would advocate for implementing this feature as a new field mapper, which would enable the creation of a custom field to hold the full URL to the source issue, e.g.:

• https://solidifydemo.atlassian.net/browse/AJMT-3

The solution must be compliant with both Jira Server/Datacenter (including older versions) and Jira Cloud.

In order to facilitate this, the Jira URL must be passed to the JiraMapper in a way that does not increase coupling. Maybe by exposing the URL on the JiraProvider.

Feel free to have a crack at it. Otherwise I might implement this as a new mapper when I have some spare time :)

[Alexander-Hjelm]

@masteragi One quick workaround for you could be to map the Jira Issue key, like I mentioned above, and then manually search replace all occurences in the exported Issue .json files with the full URL, like this:

Before:

        {
          "ReferenceName": "Custom.JiraReference",
          "Value": "AGILEDEMO-2"
        },

After:

        {
          "ReferenceName": "Custom.JiraReference",
          "Value": "https://solidifydemo.atlassian.net/browse/AGILEDEMO-2"
        },

[masteragi]

@Alexander-Hjelm, thank you for the ideas - this was exactly what I was thinking of.

[Alexander-Hjelm]

Great! :)

[cacti77]

+1 for this feature. It would be very handy to link directly back to the originating Jira issue (at least until the Jira server is shut down!). Thanks for the workaround @Alexander-Hjelm in the meantime.

[cacti77]

I was able to add a link to the Jira issue using the search-and-replace workaround suggested above. Frustratingly, however, the link that then appears in DevOps isn't clickable anyway! It's just a text string that happens to be a URL.

See also https://stackoverflow.com/questions/74428913/can-i-add-url-as-a-field-in-azure-devops-work-items-via-manually-or-through-auto and https://stackoverflow.com/questions/73978978/how-do-i-add-hyperlinks-to-the-related-work-field-on-details-page-of-azure-dev. A 'Hyperlink' type link would be clickable in DevOps but wouldn't be viewable on the Details page of the DevOps issue anyway. So adding this feature to the migrator tool would be somewhat held back by current limitations in DevOps itself, unfortunately.

[Alexander-Hjelm]

@cacti77 . Custom fields with type = Text (single line) can only show unformatted text. If you want the URL to be clickable, you could put it in the Description or another custom field with type = Text (multiple lines)

[cacti77]

Thanks @Alexander-Hjelm; I didn't know that! However my DevOps admin installed the Clickable Links extension; and I can confirm the link is then clickable. Other extensions are also available; e.g., URL Field, but I've not tried that.