search

solidify / jira-azuredevops-migrator

Tool to migrate work items from Atlassian Jira to Microsoft Azure DevOps/VSTS/TFS.
MIT License
264 stars 228 forks source link

Sprint information is not exporting #1048

Closed TKallem closed 5 months ago

TKallem commented 5 months ago

Describe the problem

I am trying to export Jira work items into Azure DevOps, I have managed to export all fields data except for Sprint information into Area Path or Iteration Path.

It looks like its not exporting for work items where there are no revisions for Sprint field.

To Reproduce

Steps to reproduce the behavior:

  1. Go to Jira
  2. Create a new user story with sprint information
  3. Try export the user story

Tool version jira-azuredevops-migrator-3.0.407

Attachments

Please attach the following files:

config-agile.json jira-export-log-240606-153325.txt

Alexander-Hjelm commented 5 months ago

I see the following messages in your log file. It seems that the iteration and area path are correctly mapped for at least 2 of the items, correct? Does that mean that the error could be on the import side?

[D][15:33:28]    Mapped value 'Sprint 11 - 2024 (2705 - 0706)' to field 'System.IterationPath'.
[D][15:33:28]    Mapped value 'Sprint 11 - 2024 (2705 - 0706)' to field 'System.AreaPath'.
TKallem commented 5 months ago

Hi @Alexander-Hjelm ,

Thank you for looking into this. Yes it worked for one Jira user story but for the other one ([DSPUBI-2390] Thiru Test User Story - Summary 3), it didn't export any sprint details.

I have attached Jira screenshot for your reference. Screenshot 2024-06-07 085049

Alexander-Hjelm commented 5 months ago

Maybe there is an issue with special characters in the sprint name? Or does the problem happen exclusively for items where the sprint has been set only on the initial revision? Or have you noticed any other pattern?

TKallem commented 5 months ago

I don't think its the special characters, I believe its to do with initial revision.

If I update the sprint information and run the export it will export the sprint details correctly.

Alexander-Hjelm commented 5 months ago

Ok! We have already identified this issue separately and are working on a patch.

TKallem commented 5 months ago

Excellent. Thank you

Alexander-Hjelm commented 5 months ago

@TKallem, I have made a PR here with a patch that fixes the issue for me locally: https://github.com/solidify/jira-azuredevops-migrator/pull/1050

Are you able to build the tool from source and try the PR out for yourself?

TKallem commented 5 months ago

Hi @Alexander-Hjelm ,

I have tested the change from your PR and it looks like it is exporting and importing the Sprint information from initial revisions fine now.

Thank you for your prompt response on this issue.

Regards, Thiru

Alexander-Hjelm commented 5 months ago

Perfect! Thank you for reporting this issue :)

Brentenbrood commented 5 months ago

1050 also fixed it for me, thanks a lot!