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
tl;dr: Advice needed on why I don't have the ability to add values to multi-select fields rather than overwrite them when using Jira automation.
I have created a new rule that when an issue is created inside an epic, the issue should check if the epic has been tagged with a specific component (ex: Engineering). If that's true, then the child issue should also be tagged with that component. That works well, but based on the standard functionality of automation, it overwrites the new issue's components completely, not adding to them.
For example: The epic was just associated with one component, "engineering." When I created the new issue I tagged it as "design," but didn't add "engineering" to the components field to test the automation. The automation then overwrote the components field to just say "engineering," rather than "design, engineering." That part, according to Atlassian documentation, is working as intended because I didn't ask it to add the component, so it overwrote it.
I want the epic's component to be added to the issue's component list, not overwrite any other components the issue was already tagged with upon creation. The documentation has steps for this, called "adding values to multi-select fields." It should work in theory, but I don't have the ability to do what the instructions say.
Instead, in my version of Jira, if I use the "copy from issue" function (called "Add components from current issue"), I lose the ability to add anything else to the field. So I can't add a second component like the instructions state I should be able to. Screenshot attached of what I see.
I had an inkling it had to do with how our Components field itself was set-up, but it's already set up to be a multi-select, here is how a ticket I have is tagged:
Any thoughts on why I can't do what the documentation noted?
Hi @Daniella Eguiguren -- Welcome to the Atlassian Community!
Context is important for automation rule conditions and actions. And without seeing your entire rule, I hypothesize you have a branching error that is causing this.
Please post an image of your complete automation rule, images of any relevant actions / conditions / branches, and an image of the audit log details showing the rule execution. Those will provide context for the community to offer ideas. Thanks!
Until we see those...
A rule structure to do what you ask could be:
Appreciate your response. Attaching my flow JIC.
I see what you are suggesting in your bullets, but that's mainly what I have. Except for the re-fetch action. Do you think that would cause my automation UI to change?
Just to phrase my question a different way: I am not saying my automation rule is not working, I am saying the Jira Automation UI I am seeing that allows me to configure rules doesn't match what the documentation screenshots are showing.
Supposedly after you select "add components from parents issue" as you and I write above, you should be able to add other components manually, as in: type them in as a list. And in my browser, I don't have the box at all. I can type in either manual component names OR "add components from parents issue." Not both.
Do you see the option on your end to add manual component names like the documentation shows here?
Thanks for that information. If I miss following up on any of your questions, please let me know...
For the UI differences, I wonder if that is both the browser / operating system differences, and changes to automation over time. The documentation does not always keep up with the product improvements :^)
I recommend adding the re-fetch to prevent / reduce the changes of any unexpected rule behavior with that Issue Created trigger.
When changing the Components field with the built-in editor, you are correct that you may either set the values (with add / remove) or copy them from some other issue...but not both at once. A work-around if you want to do both is to edit using advanced edit with JSON, as described here: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Components
You can directly enter the Components when using the SET option; that will then show the drop-down list as in your image from the documentation.
To confirm, is your rule working as expected or is there still a problem with it?