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; } } }

Transition Most Recently Updated Subtask on Parent Transition

Mathew Lederman

We are looking to use Project Automation to reopen the most recently closed sub-task when the Parent transitions from Resolved > In Progress.

To identify the most recently updated sub-task, I'm using "issue in limitedResults("Project=[ProjName]","1") ORDER BY updated DESC" from the Go! JQL add-on, but I can't figure out how to apply the transition to the resulting subtask. Below is what we've built to-date:

Any suggestions would be appreciated

Accepted answers

All comments

Florian Bonniec

Hi @Mathew Lederman

If I'm not mistaken, the second condition return all the issue from the project but limit the number of result to 1, returning the lat updated issue of the project.

It do not seems to be what you are looking for.

You are looking for something more like project = RQMTEST and parent = {{triggerIssue.key}} if it support that.

Regards

Mathew Lederman

This worked perfectly, thanks! I updated the If: Issue matches JQL to the following:

issue in limitedResults("parent = {{triggerIssue.key}}","1") ORDER BY updated DESC

Is there a reason (possibly best practice?) to include the project in the query? I tested with and without and didn't notice a difference in the time taken to complete the automation.

Florian Bonniec

Not sure, in this case parent field is already limiting the scope to the project the trigger issue is in.

Mathew Lederman

After some testing the query above didn't quite work as desired. Because the ORDER BY function occurs after the limtedResults function and not simultaneously, the query always returns the same result. We have tried to put the ORDER BY function in the limitedResults function, but the automation fails which works in a simple JQL search. However, when moved into the automation with the Smart Value it fails.

We updated the query to

issue in limitedResults("parent = ({{triggerIssue.key}}) ORDER BY updated DESC","1")

And the automation returns the following error:

(key IN (RQMTEST-174) AND (issue in limitedResults("parent = (RQMTEST-171)))" - Error in the JQL Query: The quoted string 'parent = (RQMTEST-171)))' has not been completed. (line 1, character 52)

Any suggestions?

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

automation