I have created a sub task which collects related groups of information to the master issue.
In the master issue there is a custom field that defines how many sub tasks are needed (to collect all of the information sets) each time a master issue is entered. In some cases the entry is one so no sub tasks are required.
Does anyone know how to automate the process of initiating the custom named subtask based on the value in the custom field (entered during the create issue step), and keep it going until we count down to the last instance?
Example: In create new issue; enter number of sets = 5; initial information set is already in master task; create four more sub tasks sequentially to capture set 2, 3, 4, 5; end auto collect; continue with create new issue;
Any advice is much appreciated even if some one knows it cannot be done out of the box or with a plugin. If it cannot be done out of the box fine, I just want to vet any possibilities.
I have identified a plugin which provides a customizabe transition step.
I may not be able to have the sub task creation take place in the desired sequential point in the create issue proces but if it is done as a post transition process that will suffice.
That initially looks like it will hold the code to achieve the desired sub task creation.
Once tested I will post the details.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG