Parent - child relation - not mapped correctly

[marek-dziechciarz]

Migrating using config agile (but scrum has also th e same problem).

According to this ticket which is closed: #985
Statuses are exported improperly.

Steps to reproduce the behavior:

1. Go to Jira
2. Create Epic (ROM-3644)
3. Create Story in that Epic (ROM-3643)
4. Create Task in that Story (ROM-3645)
5. Create Subtask in that Task (ROM-3646)

After the migration it loos like this:

1. Epic (ROM-3644) Has Parent (!sic) Feature (ROM-3643) - incorrect
2. Feature (ROM-3643) Has parent Story (ROM-3645) - incorrect
3. User Story (ROM-3645) has Childs
   3.1. Feature (ROM-3643) - incorrect
   3.2. Task (ROM-3646) - correct

Even when I flip Parent and Child config the situation os still not correct.

Tool version

• Version of the jira-azuredevops-migrator tool [3.0.356 ...

Attachments
jira-export-log-240322-143024.txt
config-rome-feature.json
wi-import-log-240322-143305.txt

Screenshots

[Alexander-Hjelm]

Not sure right away. Does the Export work? Do the links come along properly? Check the .json files created locally.

[marek-dziechciarz]

Nope, there is a error on the export step Story doesn't have link to task as a child because subtask has link to task as child.
So task is exported as a child of subtask not as parent.
Epic and story has proper link

[Alexander-Hjelm]

Ok! I will try and reproduce the issue in our test environment. I will let you know as soon as we know more.

[marek-dziechciarz]

Cool, especially:
Crete please:
Epic with Story as child (especially created by Add a child issue button

This Story with Task as a child

This Task with Sub-Task (ewspecially created by Create subtask button

[marek-dziechciarz]

Ok! I will try and reproduce the issue in our test environment. I will let you know as soon as we know more.

Any updates on this?

[Alexander-Hjelm]

We have been on easter holidays since friday. I have not yet had time to look into this issue, but I am aiming to do it this week.

[marek-dziechciarz]

Are there any updates on this?

[Alexander-Hjelm]

Hello @marek-dziechciarz! I have not yet had time to look into it yet. Apologies for the delay.

[marek-dziechciarz]

Is there a chance to handle this in this week?
Because i must prepare migration, and if there is real chanse to fix this then i will wait, but if not, then i must migrate using relation "releated" instead of parent-child

[Alexander-Hjelm]

It is on my todo-list. I have other priorities as well though, so I cannot say how soon I can get around to it.

We do offer professional consultancy hours, through which you can get priority support for bug fixes and feature requests!

[marek-dziechciarz]

Is there any chance for fixing this issue in future?
There was many releases since this ticket but my issue is still open