Hello all,
I only recently started using Jira and I like it very much. I discovered the automation feature and was wondering if it is possible to do the following:
When creating a task (called e.g. "AVCR") , create about 50 subtasks, that use the name of its parent (e.g. "AVCR-income" or "AVCR-performance") then I want the automation to link specific subtasks. So the "income" subtask will always block the "performance" subtask.
Is this possible? And how do I do it?
Thanks a lot!
For more information: I want this automation on a certain Projekt, where there are only tasks with their subtasks, that are always names in the same way and with the same information.
Yes you can do this. Creating 50 sub-tasks will be a bit of work but certainly doable. I would refer you to the for all the details but also use the search bar here in the Community for automation examples that may help as well.
basically it will look like this…
trigger - issue created
conditions - specific conditions to ensure you only proceed if the desired task is being operated on
action - create subtask
branch - for most recent created issue (sub-task) add link
action - create subtask
branch….
etc.
you can use Smart values to pull the “AVCR” part of task into the summary of the subtasks.
I get until that point where i want to link the two subtasks.
I just do not get, how I find the subtasks i want to link to eachother.
Any Idea?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Dominique Hermens and @Jack Brickey
Although doing this type of linking with a rule is possible, rules have a limit of 60 components, so you probably cannot do this in one rule due to the number of created sub-tasks (i.e. 50 sub-tasks).
A work-around might be that you use additional rules to have the creation of some sub-tasks (e.g. "AVCR-income") create their dependent sub-tasks (e.g. "AVCR-performance") in the same parent story. If you have just a few of these dependencies, it wouldn't be too difficult. If you instead have a whole tree hierarchy you may need to consider a different approach.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Bill,
good to know, I just found out how to link certain subtasks, so I will consider it. Maybe just trigger new rules at certain points. In that case 60 components will be sufficient, and I will just go with: If subtask with summary ~ income created then go to parent and create new subtasks etc...
I do have a whole tree and at one point we where thinking of using Rest AP but I want it to be in Jira completely.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ah yes good point @Bill Sheboy . I had forgotten about this limit I had run into this once before and had to re-factor my automation to make it work. Ultimately I created two separate rules.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.