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
Hello @Pierre Ibrahim
It’s Aleksandra from Deviniti - the vendor of the Issue Templates for Jira app.
If you’re open to using a plugin, you could use our app to create templates for Epics with Stories and Sub-tasks. Next, you could link the sub-tasks with one another using issue links and the app will reflect the relation when recreating everything from template (even if sub-tasks come from different parents).
It can be accomplished thanks to the Create structure post function we deliver that interprets different kinds of issue links in templates. For more details, I encourage you to see the app's documentation available here.
Hopefully, you will find it useful!
Please let me know in case of any additional questions about the functionality or setup and I'll be happy to assist.
Cheers,
Aleksandra
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.