From Structure to Roadmaps

[Luca Tonet]

Hello
We upgraded Jira Data Center to 8.20.6 and with that we have now Advanced Roadmaps in place. As our users are quite keen in using it (intuitive and fast) we want to know if it is possible to import whole structures from the Structure plugin into Roadmaps. Of course the hierarchy level should be the same on both parts but linkage between the issues seems to be different in both products. Have you ever heard about a similar question or requirement or any ideas how this can be achieved? The thing is that we have teams which created quite extensive structures of issues within Structure plugin and do not want to do the work a second time also in Roadmaps.

Happy for any reply
Cheers
Luca 

[David Niro · Accepted solution]

Hello Luca,

David from ALM Works here. 

I believe the short answer here is it is not possible.

Advanced Roadmaps uses two fields to build the hierarchy, Epic and Parent Link.  Structure can use these fields as well, but also allows you to build a hierarchy from any other issue link type that you have set up.

For that reason, the reverse scenario (creating Advanced Roadmaps hierarchy in Structure) would be much easier.

Recreating the structure hierarchy in Advanced Roadmaps would require mapping the existing issue link type(s) (maybe "blocks", "relates to", etc) to the Advanced Roadmaps Parent/Child relationship (which is a field).  I'm not sure if this would be possible.  If it is, it would require something like Scriptrunner to accomplish.  Even then though, you may have some issue types located in your structure that would not easily translate to the hierarchy levels you have defined in Advanced Roadmaps.

Please let me know if this helps.

Best,
David

[Luca Tonet]

Hi David 
Thanks for your answer. Somehow this was expected. I see that Structure is offering an Automation->Extend called "Child issue from Advanced Roadmaps" which is I think the tool to synchronize Roadmaps structures into Structure.
What we have so far is that we defined the Hierarchy Level of Roadmaps in a way that it corresponds to the most used hierarchy in Structure by the teams (affected teams have setup kind of standard in this direction and workflow/issuetypes are standardized as well which is obviously quite helpful when doing migrations). Nevertheless there is still some mapping and transformation effort to do in this direction (as you mentioned with eg scriptrunner) and I don't know if it is worth to invest here or just to let decide the teams where they want to do their planning. As well as we do not have scriptrunner or another jira scripting tool in place.

Thanks again, so your reply helped me to understand the missing pieces here.

Cheers
Luca