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

Max and min of versioned incidents

Leonardo Zevallos Guzman

Hello community, I need help with an automation.
I have many user stories and one epic that belong to a version "x". User stories are not related to that epic by parent/child or linkage. So what I want is that when I edit the start and end dates of the user stories that belong to version "x". That epic that belongs to version "x" captures the lowest value of the start date of all the user stories that belong to version "x" and the highest value of the end date of the user stories that belong to the version "x"

Accepted answers

Bill Sheboy

Hi @Leonardo Zevallos Guzman

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...

Your rule is probably triggered on a change to the Start Date or Due Date fields, followed by a condition to check if the issue type is a Story.

Once that occurs, your rule could use the Lookup Issues action with JQL to gather all Stories with the same version. Then the rule could branch with JQL to the Epic which has the same version, and then make the edit, using the min and max functions on the lookup results.

Please review this documentation to learn more about that action and the functions needed:

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Leonardo Zevallos Guzman

Until we see those...

Your rule is probably triggered on a change to the Start Date or Due Date fields, followed by a condition to check if the issue type is a Story.

Please review this documentation to learn more about that action and the functions needed:

Kind regards,
Bill

Leonardo Zevallos Guzman

Hello dear. I don't understand much of the documentation but I was able to get it this way

Part 1.png
Part 2.png

As you can see, the project where I am executing it is in GF. I consider it a "static" code because I am telling it where it has to do it in the query part and in the branch. Is there a way to make it more "dynamic". For example: automatically detect the project where the rule is triggered and extract all the user stories from that project with version 1.0? Or at the time of the branch that automatically detects the epic of the project that belongs to the version without having to place it specifically? I say this for the reason that I don't want to fill myself with automations for every project I do.

Bill Sheboy

Dynamically doing this with the Lookup Issues action, and the JQL branch to find the epics, is what I was suggesting: everything is relative to the trigger issue's project and fix version.

An example rule could be like this:

trigger: issue field changes for Start Date or Due Date
condition: issue type equals Story
condition: fix version is not empty
any other conditions you need
action: lookup issues, with JQL to find all stories with the same fix version. For example...

project = "{{triggerIssue.project.name}}"
 AND fixVersion = "{{triggerIssue.fixVersions.name}}"
 AND issueType = Story

branch: on JQL to find the epic, with JQL, such as:

project = "{{triggerIssue.project.name}}"
 AND fixVersion = "{{triggerIssue.fixVersions.name}}"
 AND issueType = Epic

inside of the branch...
- action: edit issue...
  - setting the Start Date to {{lookupIssues.Start date.min}}
  - setting the Due Date to {{lookupIssues.duedate.max}}

As an observation: a rule like this would be more predictable in behavior if all of the Stories are assigned to the Epic. Given your current scenario, multiple epics which are assigned to the version would all be updated, even if there are no associated stories to implement them.

Leonardo Zevallos Guzman

Hello, I get this audit error: Auditoria 1.png
Auditoria 2.png

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud