Task with highest priority of your Subtasks

[Douglas Oliveira]

Hi guys,

How do I make the Task always have the highest order priority of its subtasks?

For example:

Task - Highest
Subtask 1 - Medium
Subtask 2 - Low
Subtask 3 - Medium
Subtask 4 - Highest

[Trudy Claspill · Accepted solution]

Hello @Douglas Oliveira 

Are you using the built in Priority field?

If so, then a rule like this works.

[Douglas Oliveira]

Hi @Trudy Claspill ,

Yes i am using the built in Priority field.

But I dont have this option to edit.

I only can Set ou Copy in this option.

I am using a business project and i am the administrator.

[Douglas Oliveira]

I was able to enter the code but it didn't work...

[Trudy Claspill]

Yes, you would use the SET option and type in the smart value.

Please show the details of your automation rule and the details of the Edit Issue step.

Could you also paste as text the message in the log, so that I can run it through a translation app?

[Douglas Oliveira]

Hi @Trudy Claspill , sure.

I change the Jira Languanges and this is the rule and the audit log:

[Trudy Claspill]

Where you have used the smart value to set the priority field, the "i" in "lookupIssues" needs to be capitalized.

[Douglas Oliveira]

Thanks

I hadn't really seen this detail but unfortunately the watering doesn't work.

The translation of the text would be marked:
The selected priority is invalid. (priority)

[Trudy Claspill]

Are you working with issues in a Team Managed project or a Company Managed project? That information will display at the bottom of the panel on the left when you are viewing the project or you can find it in the Type column on the View all projects page.

I tested the rule I provided against both types and it worked.

Please add a step after the Lookup Issues action to print the smart value for the count of issues found into the Log. This is done with the Log action. 

Lookup Issues count: {{lookupIssues.size}}

Please add a step before the Edit action to print the smart value into the Log. This is done with the Log action. Print both the value and the name associated with the value.

Parent priority is: {{lookupIssues.first.priority}} / {{lookupIssues.first.priority.name}}

Run the rule again and review the log. It should show you a numeric value for the count of issues found by the Lookup action and a numeric value for the priority and the text name displayed for that priority.

Is the count of issues found greater than zero?

Is the priority value a value that you could set manually on the parent issue?

[Douglas Oliveira]

Thanks for answer @Trudy Claspill ,

This was the result of the audit log.
I'm using a company-managed proje

[Trudy Claspill]

That confirms that the Lookup is finding issues, and the first one in the results set does have a valid priority value.

Can you show us the details of the Edit step again, since you changed it? I want to confirm that is contains the following without any typographical errors.

{{lookupIssues.first.priority}}

When you were entering the smart value, did is show you the pop-up below the field as you typed? And did you click in that area to insert the value you typed into the field?

[Douglas Oliveira]

It worked now, There was a space at the beginning of the smartvalue text...
Thank you very much @Trudy Claspill !

[Douglas Oliveira]

Thanks @Trudy Claspill 

I hadn't really seen this detail but unfortunately the watering doesn't work.

The translation of the text would be:
The selected priority is invalid. (priority)

[Dave Mathijs]

HI @Douglas Oliveira 

In which view would you like to achieve this?

A Task is always the Parent of its Subtasks, just as subtasks are always the child of their parent, the Task.

You can drag and drop the subtasks of a Task up and down (ranking) to determine the "priority".