Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation rules with JQL SELECTOR and UPDATE FIELD with parser expression

Isabel Fonseca July 3, 2025

Hellow,

Problem:

Automation Rule don't do anything.

Steps:

Automation Rule:

project in (SUP) AND "resolved" <= -8w AND level != "Contains personal data" and issueFunction in linkedIssuesOf("issuetype = 'problem task' and resolved <= '-8w'")

 

1.png

 

Example:

  • SUP-91930 Problem Task

2.png 

  • There are two ‘Parent’ that are Solicitation

3.png4.png

The goal is to load the ‘Data Level’ for each SUP resulting from the JQL selector, inheriting from its parent.
But the automation doesn’t update anything.

 

Any suggestions?
Best regards

 

 

2 answers

2 accepted

4 votes
Answer accepted
Trudy Claspill
Community Champion
July 3, 2025

Hello @Isabel Fonseca 

What app are you using to create that automation? It doesn't appear to be the native Automation for Jira app.

What version of Jira Data Center and what version of that third party app are you using?

Have you first confirmed that the JQL selects the correct issues?

If so, then I think the problem may be that you have created an artificial parent/child relationship using generic issue linking, and the automation doesn't consider the linked CAR-AT issue to be the "parent" of the SUP issue.

When you provide information on which third party app you are using, then perhaps I can find more information in the app's documentation.

qsjira_cleva_pt
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 8, 2025

Hello @Trudy Claspill

First of all, I apologize for the delay in responding.

I am using "Jira Data Center v9.12.19".

I have first confirmed that the JQL selects the correct issues: 

JQL_1.png

 

 

Isabel Fonseca July 8, 2025
  • "Automation rules"

Automation_0.png

  • "SUP | Update Data Level "

Automation_1.png

Trudy Claspill
Community Champion
July 8, 2025

Did you use the Expression Parser Test Page to test the expression you are using against one of the issues retrieved by the selector?

Trudy Claspill
Community Champion
July 8, 2025

Also I'm having trouble finding information in the JWT documentation about using "selector." as part of the expression. Do you have a link to reference material that demonstrates that usage?

Isabel Fonseca July 9, 2025

Hello @Trudy Claspill ,

Documentation:

https://apps.decadis.net/display/JWTSDC/Update+field+action

https://apps.decadis.net/display/JWTSDC/Data+types

 I am doing some tests. If I find a solution, I'll let you know.

Many thanks.

Best Regards

1 vote
Answer accepted
Sergio García-Consuegra _Decadis AG_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 9, 2025

Hi @Isabel Fonseca ,

My name is Sergio, and I'm a member of the support team from Decadis. I will assist you with your current doubt.

When you select the "Parent" value for a specific custom field, you are referring to the parent of a sub-task. In this case, you are using the link type "parent of", which is not a hierarchy between a sub-task and the parent, as you can find int the "What is the context" section of our Field codes page from our documentation: https://apps.decadis.net/display/JWTSDC/Field+codes 

However, you can still achieve your current requirement using the following expression in "Advanced text" mode for your Update field action in your Automation Rule:

first(fieldValue(%{issue.cfNNNNN}, linkedIssues("link type")))

Just replace "NNNNN" for your "Data" custom field code. And "Link type" for your link type name. I saw in the screenshots that you use in the parent the link type "parent of". So instead, you should use the link name which appears in the "child" issues that have this linktype.

This is an example of how the "Update field" action looks in my instance:

UpdateField.png

In my case, my custom field code is "10108". As mentioned, the parsing mode is "Advanced mode"

In case you have any other doubt or if it doesn't work as expected, please let us know. I will gladly assist you :) 

Also, we have a customer portal where you can contact us with this doubt or any other doubt you might have in the future! Here you have the link to our customer portal: https://decadis-apps.atlassian.net/servicedesk/customer/portals 

Thanks!

Best regards,
Sergio

 

Isabel Fonseca July 9, 2025

Hello @Sergio García-Consuegra _Decadis AG_ ,

Good news, my situation is resolved.
Many thanks for your awesome support

Is solved.

 

first(fieldValue(%{issue.cf35707}, linkedIssues("subtask of")))

Solved0.png

Solved1.png

Best Regards,
Isabel Fonseca

Sergio García-Consuegra _Decadis AG_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 9, 2025

Hi @Isabel Fonseca ,

I'm happy to hear the solution was useful for you!

If you have any other doubt related to our app, please feel free to create a new request in the support portal I mentioned in my previous message.

Our support team will gladly assist you!

Have a nice rest of the week 😄

Best regards,
Sergio

Like Isabel Fonseca likes this

Suggest an answer

Log in or Sign up to answer