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
Hi Atlassian Community,
I have a single project with 2 issue types: A and B
In Issue Type A: Ticket 1 contains parent and sub-tasks with the following category/sub-category: A/A
I would like to clone Ticket 1 to Issue B along with the sub-tasks.
However on the parent ticket for Issue A, if Category/sub-category is A/A --> in the destination issue type B, the category/sub-category would be updated to B/B
On the sub-task ticket for Issue A, if category/sub-category is A/A --> in the destination issue type B sub-task ticket, the category/sub-category would be updated to B/B
For some reason I'm not able to get the Category/Sub-category custom field values to be updated in the sub-task portion.
Here are screenshot for reference.
Am I missing something for the sub-tasks?
Hi @Mary Mark
For a question like this, I recommend posting an image of the complete rule, images of the relevant actions / conditions /branches, and of the audit log details showing the rule execution. Those will provide context for the community to offer suggestions.
Until we see those...
Your question description uses "A" and "B" to represent issue types, issues, categories, and sub-categories...so I'm going to ignore those for a moment as I am not understanding those.
It seems you are having a problem using advanced edit with JSON to update the newly created sub-tasks for their Category and Sub-Category. And that field appears to be a cascading field.
The JSON looks okay to me, and I hypothesize the problem of not updating correctly has two causes: rule timing and scope.
The subtasks are cloned in a branch on more than one thing, and then apparently edited outside of the branch. Branches on more than one thing are run in parallel and asynchronously, and so the branch will not complete before the next steps in the rule. For your scenario, it may be better to include the advanced edit at the same time the issue is cloned.