Migrated shows "Closed" as first state

[gnimor]

I am trying to import our JIRA server entries to Azure Devops. The migration completed without error, but I have a strange behaviour. In the history of all imported entries the first state is "Closed" instead of "Proposed" or "Active". I have attached the history of an imported item:

History in Azure Devops:

Original history in Jira:

and the state mapping is as follows:

	    {
          "source": "Pending",
          "target": "Proposed"
        },
		{
          "source": "IN PROGRESS",
          "target": "Active"
        },
	    {
          "source": "VERIFIED",
          "target": "Closed"
        },
	    {
          "source": "Open",
          "target": "Active"
        },	
		{
          "source": "RESOLVED",
          "target": "Resolved"
        },
		{
          "source": "Closed",
          "target": "Closed"
        },			
		{
          "source": "Reopened",
          "target": "Active"
        },
		{
          "source": "UNDER TEST",
          "target": "Test"
        },			
        {
          "source": "To Do",
          "target": "To Do"
        },
        {
          "source": "In Progress",
          "target": "Doing"
        },
        {
          "source": "Done",
          "target": "Done"
        }

[Alexander-Hjelm]

Strange behavior indeed. Marking this as a bug.

Any chance you can share the migration log file as a pastebin? @gnimor

[gnimor]

@Alexander-Hjelm: What log files do you need? wi-import or jira-export log?

[Alexander-Hjelm]

Both if possible!

---

From: gnimor @.> Sent: Wednesday, July 6, 2022 1:39:32 PM To: solidify/jira-azuredevops-migrator @.> Cc: Alexander Hjelm @.>; Mention @.> Subject: Re: [solidify/jira-azuredevops-migrator] Migrated shows "Closed" as first state (Issue #491)

@Alexander-Hjelmhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAlexander-Hjelm&data=05%7C01%7Calexander.hjelm%40solidify.dev%7C3853ec46dfb54be7d7cd08da5f4432b6%7C1f39fa86968941dab81ed60e10615bf0%7C0%7C0%7C637927043761808336%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3ce5dz2BV7ZZWeITqWPmiU79NvLoy5XZxm%2BUoCU38qg%3D&reserved=0: What log files do you need? wi-import or jira-export log?

— Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsolidify%2Fjira-azuredevops-migrator%2Fissues%2F491%23issuecomment-1176116867&data=05%7C01%7Calexander.hjelm%40solidify.dev%7C3853ec46dfb54be7d7cd08da5f4432b6%7C1f39fa86968941dab81ed60e10615bf0%7C0%7C0%7C637927043761808336%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=PPGoOGh5ICZt4OoQoGDNwjbO5BkYv68HRENRL5fEWUE%3D&reserved=0, or unsubscribehttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACRQL6B4DLOYZC5V5GIINXTVSVV7JANCNFSM52Y36TKA&data=05%7C01%7Calexander.hjelm%40solidify.dev%7C3853ec46dfb54be7d7cd08da5f4432b6%7C1f39fa86968941dab81ed60e10615bf0%7C0%7C0%7C637927043761808336%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7rq%2FOpPcqPhSAxJYsxLpL51rUJC3qeTYWOrJtJum2b4%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>

[gnimor]

Sure..

jira-export-log-220706-082414.txt

wi-import-log-220706-082605.txt

[Alexander-Hjelm]

I see nothing immediately wrong in the logs, so probably a bug in the tool.

Let's keep this open as a bug report. Sadly I can't give an estimate on how long it will take until we get to fixing it, but we welcome the community to have a crack at it in the meantime :)

[rambaliga]

Hi @Alexander-Hjelm , any idea if there will be a fix for this anytime soon? We are facing the same issue with the tool.

[Alexander-Hjelm]

@rambaliga No estimate unfortunately. Since we don't have any direct funding for the jira-azdo migration tool, we can only work on it as soon as time allows us to. But we always welcome community fixes :)

If you are in urgent need, or if we can help you with your migration in some other way, you are always welcome to make a business inquiry to Solidify AB, Sweden.

[Alexander-Hjelm]

I have tried to reproduce this behavior, but haven't been successful. Everything seems to works fine. so I'm relabeling this as a support issue.

@gnimor , @rambaliga . Do you have any additional info that could help with reproducing this issue? Have you identified any patterns, whether this issue happens for some work items but not for others?

Have you tried both the latest Release and the latest version on the master branch?

[github-actions[bot]]

This issue is stale because it has been open for 25 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 5 days since being marked as stale.