Automation rule to heritate "components" field from test plan to test execution

[Admin Jira]

Hi,

I’m using Jira with the pluggin XRay. I tried to implement an automation rule to update the “labels” and “components” fields of a test execution whenever the execution is linked to a test plan. For that I’m using the field value changed trigger on the “test plan” attribute of the test execution. So when i add an execution to a test plan, it should be triggered. However, the rule is only triggered when I modify manually the field “test plan” in the test execution. but if i add the execution to the test plan from the test plan issue, then the rule is not triggered. Do you know why it is like that and how I could get the rule to works in both directions (from the test execution and from the test plan)

Thanks in advance

[Admin Jira]

Here is an image of my complete automation rule with the script that I use.

I think the problem is probably like you said that the action performs by XRay is not considered as an event by Jira Automation, so  it does not trigger the rule.

[Bill Sheboy]

I recommend contacting XRay, either through their documentation or support team, on their marketplace page.  They will be better able to answer this question.

[Admin Jira]

I tried but they don't really know about automation and told me to reach atlassian support

[Bill Sheboy]

That is curious; I would expect the vendor can tell you if the actions you are taking do / do not raise events that can be detected by Jira.

Also, this is a community forum and not Atlassian Support.  If you are on a paid Jira license, you can contact Atlassian Support here: https://support.atlassian.com/contact/#/

[Bill Sheboy]

Hi @Admin Jira 

First thing, I am not using XRay and so my suggestions are based on my experience with automation rules, in general.

Next, for a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Until we see those...

When a rule does not trigger as expected, there are several possible causes.  For example:

• Some marketplace addons perform actions which do not appear as events to Jira automation, and so do not trigger rules
• A different event is happening than the rule trigger uses.  Such as an issue updated versus created.
• When an automation rule performs some action, by default that does not trigger other rules.  This is to prevent errors and unnecessary rule looping.  When it is desired that the actions of one rule can trigger other rules, the "downstream" rules should enable the "Allow Rule Trigger" option in their details.  Please use caution with this option to prevent unintended consequences.
• etc.

Seeing the specifics of your rule(s) may help clarify what is happening.

Kind regards,
Bill