Migration :the issue type Review from one project to another

[mummareddy supriya]

Hey everyone, 

I have a question regarding issue type migration. Here are the details:

- Migrate issue type  Review for Project A to Review subtask for project B , while moving the review type to reviewsubtask from project A to project B it is asking for linking for story 

I need help here ,how can i proceed with this ,this is 1st time i'm working on this .thanks in advance.

1- Link each reviews to story while mapping/Moving
reviews --- can not with out story,first you will move the stories, 2nd through script you'll link the review as review subtask?

2- Create one dummy story in EDF project and Link all the reviews to that story while moving, later we can delink and link to respective story

[Dick]

Hi @mummareddy supriya 

The feedback you get from Jira is quite spot-on here. You cannot have a orphan sub-task work item, it needs a parent. Jira invites you to fill in the parent key, so it can maintain the parent-child relationship you desire (by wanting to change the work item into a sub-task).

If you haven't got a parent work item, then you should create one prior to the move action.

Kind regards,
Dick

[mummareddy supriya]

@Dick  Created one dummy story in EDF project and Link all the reviewssubticket to that story while moving, later we can delink and link to respective story. I must link that review subticket to the story if the summary is the same. How can I accomplish this?Which is possible, utilizing automation rules or groovy scripts?Please let me know how to proceed. 

[Dick]

Automation is certainly possible. I have no experience with Groovy scripts.

Note that you won't get into trouble when the summary is the same for multiple sub-tasks, as their key will be different.

Kind regards,
Dick