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'") Example: * SUP-91930 Problem Task * There are two ‘Parent’ that are Solicitation 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

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation rules with JQL SELECTOR and UPDATE FIELD with parser expression

Isabel Fonseca_fndlo5

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'")

Example:

SUP-91930 Problem Task

There are two ‘Parent’ that are Solicitation

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

Accepted answers

Trudy P Claspill

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.

Sergio García-Consuegra _Decadis AG_

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:

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

All comments

Trudy P Claspill

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?

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

Hello @Trudy P 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:

Isabel Fonseca_fndlo5

"Automation rules"

"SUP | Update Data Level "

Trudy P Claspill

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

Sergio García-Consuegra _Decadis AG_

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.

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")))

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

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

Thanks!

Best regards,
Sergio

Isabel Fonseca_fndlo5

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")))

Best Regards,
Isabel Fonseca

Sergio García-Consuegra _Decadis AG_

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-data-center

data-center