Attempting to update Radio Button in Epic based on change to (parent) capability

[Scott Campbell]

Hello all,

I have epics and their parent level of capabilities that both have mandatory radio buttons. I want to create an automation where when I change the capability of an epic, the epic automatically changes its mandatory radio button to match the capability. 

I have tried several options but so far have yet to get any successful results. Any assistance would be helpful. 

[Scott Campbell]

Hello John,

When: Issue updated

If: Issue Type equals: Epic

For Parent

If: Mandatory equals: Yes

Then: Edit issue fields: Mandatory - Yes

Else

For Parent

If: Mandatory equals: No

Then: Edit issue fields: Mandatory - No

[John Funk]

Hi Scott - Welcome to the Atlassian Community!

Can you share the rule that you have so far and where it is not working as you desire?

[John Funk]

Please reply in line here so that other readers can follow the train of the conversation. 

Can you post a screen shot of the actual rule please? That way we can see the level each item operates at. 

[Scott Campbell]

As you can see, I am trying to make my Epics match their mandatory field to the next step above them (capabilities). However, after verifying that the mandatory fields differ between the epic and capability, no action is performed. 

[John Funk]

Well, what happens is that the second Condition is failing so the rule stops. So it is NOT verifying that the values are different. Can you share the details of that IF statement? 

[Scott Campbell]

[John Funk]

Maybe it doesn't like the field name Mandatory as that might be a reserved word. Try using the {{smart values}} condition along with the field ID. 

In the example below 10134 would be the id of your Mandatory custom field. 

[Scott Campbell]

It looks like the if.matches works based on the custom field ID, however the edit function is still failing. 

[John Funk]

So both Conditions are passing now - that is good. 

Can you share the details of the Edit issue for the Mandatory field? 

[Scott Campbell]

[Scott Campbell]

Also I wanted to say thank you for bearing with me through this one John. 

[John Funk]

So, if it is the parent level field value that is changing, and you want to copy that down,

then you will need to add a Branch for Children between the two Conditions. And move the second Condition and subsequent field update under the branch. 

[Scott Campbell]

I Confirmed that the value of the custom field matches in both the parent of the Epic and the Epic itself. Below is the error and the new flow: 

[John Funk]

Try adding a Log action for the value of that field after the second condition. 

[Scott Campbell]

Ok, the log action did recognize that it is listed in the "no" position however it still fails to execute the edit to match it to the parent above it. Is it possible that since the item child parent relationship is an Epic to Capability relationship, that the term "parent" isnt functioning the way I want it to? 

[John Funk]

So, what are the values in the two fields? And which field did you do the log action on? Parent or the Epic?

[Scott Campbell]

The values of each field are a radio button selecting either Yes or No. The custom field number for both fields is the same, 32090. The log action done was on the Epic. 

[John Funk]

But in your example - what are the current values of each field? 

[Scott Campbell]

The current value for the Epic is No. The current value for the Capability is Yes. 

[Scott Campbell]

As an update. I have found that jira is unable to execute a log action against {{issue.parent.customfield_xxxxx}}. My guess is that "parent" is not accepted for items above Epics. I have attempted to use capability and feature, both of which did not work sadly. I would also assume that means that the advanced compare is not executing properly if the system cannot log the position as previously mentioned. 

[John Funk]

Okay, that's good to know. Let's try this - simply take out the Compare condition and see what happens. 

[Scott Campbell]

Still the same issue, as I think it is something to do with the "Parent" and what that phrase identifies. 

[John Funk]

I am wondering if it is the type of field. See if you can add a different type of field and do the same thing with copy from Parent issue and see what happens. Maybe Due Date or something like that. Just make sure there is a value in the Parent issue for that field. 

[Scott Campbell]

Sadly does not work, which reinforces the perspective I have regarding "parent" not applying to items above Epics: 

[John Funk]

So the Epic has a value in the Parent field. Is the Parent in the same project? Or a different project? If different, are you sure you have full permissions to that project? Is the rule a single project rule? Or have you included both projects in a multi-project rule? 

[Scott Campbell]

Same project, only a single project. I have admin access. Both the Epic and Capability have the same fields (now tested Mandatory field and Priority field). 

[John Funk]

Last question before going to support  - Are both of those fields on the Create and Edit screens for that project? 

[Scott Campbell]

Yes, and confirmed they are both listed on the "View issues screen" within the "field" tab for both issue types (Epic and Capability)

[John Funk]

Not the view issues screen, but the Edit screen. 

[Scott Campbell]

Yes, it is there as well for both. 

[John Funk]

Sorry dude, I am all out of suggestions. You should probably open a support ticket with Atlassian to see if they can help. Please post back here with the solution for future readers. 

https://support.atlassian.com/contact/#/

Good Luck!