You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
New Jira admin here, I am trying to track how some existing tickets create new tickets. I can follow the bread crumbs up to the point where I find a post function referencing what appears to be a variable.
Did some research this appears to be an application add-on for our Jira called 'Create on transition' by Bob Swift.
I don't see how that variable or tag(Create multiple issues: %Client Services Termination Tasks%) or whatever is being called, bobswift documention mentions how to create one (https://bobswift.atlassian.net/wiki/spaces/CSOT/pages/454787190/Create+multiple+issues+-+7.x)
however it's not clear to me how the variable is translating into 7 sub-tasks created.
Hi @David Cook ,
Thanks for reaching out to us!
Can you please check and let us know if the custom fields named Client Services Termination Tasks, Backoffice Termination Tasks are multi-value fields? If yes, then do they have 4 values each for an issue? If that is the case, then each value will create a subtask according to your post function configuration.
It would be great if you can share the issue view screen of the issue where both the fields are displayed with values in it.
We have created a support ticket in our portal on your behalf and marked you as reporter. Please access it here https://bobswift.atlassian.net/servicedesk/customer/portal/1/SUPPORT-7544 and continue to follow that ticket for further updates on the progress.
We hope this helps!