I'd like to be able to automatically create a bunch of linked issues when creating a single issue.

[Michael Clark]

We have a workflow that involves a lot of different steps, and each step touches a different department.  We use blocking links on each task to make it obvious where an asset is through this pipeline, and what I would like to do is something like this:

Create a master task "Cool Asset", that, on creation, makes the following tasks and links them:

Cool Asset Design, which is blocking

Cool Asset Art, which is blocking

Cool Asset Implementation.

Bonus points if I can somehow automatically fill in the estimates for each of those steps based on information in the master task.

My actual pipeline has about twice as many steps.  We do it this way to provide visibility to all departments and to be able to track departmental capacity, so other solutions would need to take this into account.

My assumption is that this is scriptable on a post-function for creation of the master task, but I'm not sure where to go to learn about custom scripting as the default scripting options available do not support linking or creation of new tasks, only sub tasks.

[Betsy Walker {Appfire}]

Hi Michael,

Darren and Volodymyr are correct in that the Create on Transition for JIRA add-on should do the trick for you.  This recipe shows how to use the add-on to automatically create a Story when creating an Epic, and a similar process would be followed for your Use Case.

You might also be interested in the Update on Transition for JIRA add-on, which you could use to automatically transition (or comment or update) the original issue when those blocking tasks are completed. This recipe shows how to add a comment on linked issues, but you could also opt to transition them.

Thanks!

[Volodymyr Krupach]

Try "Create on Transition for JIRA" suggested by Darren Pegg. If it does not suit, you need to create the custom addon or groovy script. Recently I created the addon that parses hierarchical JSON with configured issues and their relations and bunch of issues is generated based user choices.

[Darren Pegg]

https://marketplace.atlassian.com/plugins/org.swift.jira.cot

[Brian Ross]

I have been doing some work in Zephyr and using their importer to bring test cases into JIRA.  In using that tool, there is a way to import tasks.  You might want to play around with that to see if you can get it to do what you need.

I have been trying to identify some of the gotcha's in using the import tool along with some other users, so it should be pretty easy to learn at this point.

Good luck.

[Darren Pegg]

You could create a groovy script that executes an xml file outlining all the attributes you require... This isn't a 5 min task to create though.. I'd recommend maybe you pay for development of that level of detail