Currently we're leveraging the Atlassian API along with a python script to create JIRA "templates" from Excel spreadsheets. However I would like to potentially move away from that and have the following issue structure:
1. Epic (representing a single template)
2. Stories (representing summary tasks that would house our workable tasks)
3. Sub-tasks (representing the actual workable tasks)
I saw some marketplace addons that would allow you to clone epics along with their stories and everything, and have the stories link to the newly created epic. However my issue is mainly the links between the sub-tasks.
We use another Marketplace add-on, BigPicture, and we use a lot of the Gantt specific links (Start to Start, Start to End, etc...), so subtask 5 from story 3 under Epic 1, could be in a START to START relationship with subtask 2 from story 8 under Epic 1 for example.
Using the cloning ad-ons would clone Epic 1 into Epic 1-New for example, and all the stories along with their subtasks would be cloned, however the following situation would happen:
Subtask 5-New from Story 3-New under Epic 1-New would be in a START to START relationship with Subtask 2 from Story 8 under Epic 1 INSTEAD OF being in a START to START relationship with Subtask 2-New from Story 8-New under Epic 1-New.
Is there a way to bridge that gap and have newly cloned issues have their links adjusted to the equivalent newly cloned target issues?
A native solution would be best but if it's only a marketplace ad-on, that's okay too.
Thank you all in advance,
Pierre Ibrahim
