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
Next: Root
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
When creating a new story, task, bug, I'd like to add a label ("kanban") to it but only if the parent also has the "kanban" label as well.
I managed to copy all the labels from the parent. But I can't figure out how to do it conditionally (e.g., only in the parent has the "kanban" label.
Any suggestion?
Thanks,
Olivier
Hi @Olivier Reuland -- Welcome to the Atlassian Community!
Where are you trying this? If in an automation rule...
Please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!
Until we see those...
You could add a condition to check if the label is present in the parent in a variety of ways. Once you share the rule the community can suggest ways that fit with your current rule.
Kind regards,
Bill
Hi @Bill Sheboy ,
I have been trying dozens of options, but nothing worked so far.
Here is what I currently have, which doesn't work. it seems to edit the parent, not the new work item. It is probably not the right way to do it, and could create more confusion for people.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that image, and FYI to try to stay in one thread when posting. That helps others see if there are multiple ways to answer a question.
Your rule is branching to the parent to check the labels, and so the edit then takes place on the parent.
And, as written, this will run for story / subtask pairs also. Are you using subtasks?
Let's assume you are not using sub-tasks, for now...
An issue with a parent can access the parent (and its fields) with {{issue.parent}} and so your rule could change to:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.