Existing field is a two level dropdown list with below values for example:
First dropdown: X
Second dropdown: Y (Z)
That means the field value as a whole is: X - Y (Z)
Now, when I run the JIRA automation rule, it should split the above values into X, Y and Z and populate another three jira fields with these values, like, say,
Field1 with value X
Field2 with value Y
Field3 with value Z
Thanks for the update.
Take a look at this previous post for some guidance. That should get you Field1 and Field2 but I am not sure how you will get Field3 since it is included in the second half (child value) of the field.
Thanks. However, the requirement is to have Field3 value too as I mentioned.
Also, Field1, Field2 and Field3 are the real fields in JIRA that need to be populated for the JIRA card/ticket which is being processed, which has the value 'X - Y (Z)' for the target field which is to be extracted.
We have already started planning for a better way like that, which can best fit to our system in place at present.
But again, JIRA automation, if possible as asked, can help us move the values from old two level dropdown field to those three new fields, for cards already populated in that way and can continue to use the automation in this way until the new system changes are in place in a full fledged manner.
Regardless, can you please confirm if that use case is possible or not?
Hi @Amit Gandhi
your requirement should be met by the following rule. Please double check if this is what you were looking for.
In case of questions Community is happy to assist.
From your description I seem to have understood the field (here Business Unit) is structured the following, data should be split into BU1, BU2, BU3:
This is the rule which is doing that:
Please note: The Trigger "Issue commented" is just an example, you can choose the trigger that suits the best.
The "Edit issue fields" actions are as follows:
In case it is a cascading select field you can just use the name, like in my example.
Otherwise or if you want to understand the whole topic better, here is the corresponding documentation:
Will this work if BU1, BU2 and BU3 are read-only text fields?
I tried with one automation test rule in which the rule ran successfully showing field edited successfully but the field was not updated as expected.
I basically want these fields to be populated/edited through jiira automation ONLY.
I cannot imagine it would work when you try to put values into a read-only field.
This would be a bit counter intuitive even from a code's perspective.
While reading your question again I think you might be asking that you want it to have updated/edited by automation but protect it from an user editing it afterwards, manually.
Yes, this should be possible when to take the field away from "edit screen".
Pre-receive hooks that verify the Git commit message, the modified files, and implement similar code change controls used to be requirements of large enterprises working in regulated industries only....
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event