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
Hello everyone, I'm trying to make automation for edit value for "Component" field.
My case is to add the extra component if the filed doesn't have it for concrete issue type.
I'm trying to use this instruction, but unfortunately I can't do it. I don't understand why?
In my case, function always edited the field and delete other components which users added before the ticket's creation.
Can you help with this?
Are you using the "add to multi-select" method instead of "set value"?
I'm a little bit stuck on this - the screenshot I would want to give you is the one that is already in the documentation you linked to! It shows you how to use "add to multi-select" in an automation. Automation doesn't have any permissions on individual functions in it, you can either create and edit automations or you can not.
Where are you stuck with following the doc? Or are you not able to add an automation?
What functionality don't you have? Your automation's "action" section doesn't contain an Edit issue function at all? Or you don't get offered something when adding an edit action?
I don't have an ability to choose the variant "Copy from issue" and additionally add "Component 2".
Because if I just mentioned set the concrete value, It will rewrite others components which were adding when issue was creating.
Look at my screenshot in the desc and compare it with in instruction. See the differences? That I'm talking about.
Does it not appear when you click the menu elipsis ... to the right of the field, where all the dynamic options are?
I'm not sure where you are stuck now - you've got the "copy from" in the ... menu, so add that to your rule, and add the component you want to add as well.
The explanation as to why you do it this way:
A multi-select field like components contains a list of options (0, 1 or many).
If you use just set "component to X", then you're overwriting the current content with a list that just contains X. Similarly set "component to X and component to Y", you're telling it to replace the content with a list containing X and Y
If you use "copy from" and "component to X" you're saying "read current list and add X to it"
I totally understand how it should works, but I can't set the parameter "copy from" and add "component to X".
I can choose only one variant - "copy from" or "set the value", no additional functions.
If I add the extra function as a separate:
If: find my issue type
Then: set the value - "My component"
And: copy from current issue
It also didn't work.
I think you don't understand what I mean.
If you're using the cloud jira, just try to repeat this automation.
I understand what you are trying to do, it is you not understanding what the functions are doing.
What do you mean by "I can only choose one variant"? If you just mean it only lets you add one of them to the automation, then that is exactly right - the functions can't be used at the same time, as they would try to make different and incompatible changes to the data in the field.
Yes, but all I would do is give you the screenshot you have included, that's showing you what Cloud does.
For anyone else running into this issue, multi-select fields give the option for "Set value" which only gives the option to select an option already in that multi-select list. Alternatively you can type in a smart value AND select something in the list.
Otherwise the "Copy from..." option only allows you to copy the value from one field into the select field which does allow you to add to existing values but that assumes you have another field with that information. Otherwise you're copying the existing values into the field as-is.
If anyone has found a way to use automation to add new selections to a multi-select field without overwriting the existing selection that works, please share.
Here you have an answer for the Atlassian team where explain this in detail and it's working properly.