Hi,
I want to create a simple rule that automates setting the custom field of issues inside an epic as soon as the same value is changed in an epic. It's really extremely simple. My problem is, that I can see in the logs that the rule was executed successfully, I can also see the correct issue IDs that should have been affected by the execution. But when I check the issues the custom field is unchanged. Can anyone help here?
Thanks & BR,
Christian
Hi @chg
FIrst of all:
Most likely the value is null, therefore no change.
thanks for the reply! It logged this:
As far as I understand this, this looks fine (at least toString is not null...)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What do you place in the Edit Issue component?
Is the Hub field visible on the Epic's stories?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"What do you place in the Edit Issue component?"
--sorry, I don't understand the question
"Is the Hub field visible on the Epic's stories?"
-- Yes, that's how I found out that something is wrong. The values of the field on stroy level did not change.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
After the branch rule, you have place an Edit Issue action (rule component). Within this component you have selected to edit the Hub field. I need to know what value you place inside that field. Did you select the choice "copy value from trigger issue", or something else?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Alex Koxaras _Relational_ You pointed me in the direction, now it works. I did not copy the value from the trigger issue but the current issue. Which, obviously, will not work. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good to know that it worked out!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @chg , welcome to the Atlassian Community!
Please check the audit log. Even if the rule is successful, the action might be skipped because the condition isn't met.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Dave Mathijs ,
thanks for the reply. I checked the audit log, that's why I am confused. It says the following:
it also states the correct ID of the issue that triggered the rule by changing the field and the correct IDs of all issues withing the epic. Looks totally fine to me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You don't have 2 custom fields named Hub by any chance?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I thought about this too. The custom field was named "Team" before (and the automation did not work), but since there are other fields with that name, I thought that this is maybe the issue. So I re-named the field to "Hub", but it didn't help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Was the field "Team" actually a custom field? Because Jira uses a couple of Team fields, for Tempo, for Advanced Roadmaps. It's best not to change the name of custom fields created by apps.
Do you have a screenshot of that custom field and type?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Dave Mathijs ,
I know about the "untouchable" fields, I really only updated the custom field I created.
Does the screenshot provide enough information?
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.