I am trying to update the Epic Baseline Dates based on Sprint Dates of the Stories. For example: * If any story is moved into Sprint 1 (assuming Dates are added to Sprints), then the Baseline (or Target) Start on the parent Epic would update to the first day of the Sprint * If any story is moved into the last Sprint (assuming Dates are added to Sprints), then the Baseline (or Target) End on the parent Epic would update to the last day of the Sprint * If any stories are moved to later / earlier Sprints, the Epic would update accordingly I have the Target Start / End dates updating on Stories based what Sprint they are moved to, but I cannot figure out how to update the Parent issue dates. This is the closest example I can find: Jira automation template library | Atlassian I hope that makes sense... Thanks for your help in advance!

Ok, well that's unfortunate. Guess all that for nothing! Ha! That's OK, I learned much. I will open a new ask for Structure Baseline. I will tag you, maybe you can help!

At this time...the lookup issues action is only available for the Jira Cloud and Jira Data Center versions of automation. With the changes to the Jira Server lifecycle, it is unlikely that action will be added. And so, a more complicated work-around is to use the Send Web Request action, calling an issue search with the REST API. That would use the same JQL as you would have used for lookup issues, and then provide a list of issue as before. Please discuss approach with your Jira site admin before proceeding. If you want to try this approach, here is a how-to article and a reference to the REST API function: * https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 * https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/#api/2/search-search

Thanks again for responding so quickly! You rock!! * I do not have a "Lookup" action available when I go to add a new action. I supposed I Can check with our admin to make sure and see if those can be added. * You stated: Perhaps it would be better to just the Epic's date fields to the min (or max) from the child issues, when needed. Would this be what Trudy added to the other discussion? Within the branch you could use the Lookup Issues action to retrieve all the child issues of that Epic via JQL where the field you monitored in the Trigger (Start Date, or Due Date) is not empty, and order the results by that field so that the first issue listed would have the date you want to copy to the Epic. i.e.: "Epic Link" = {{issue.key}} and "Start Date" is not empty ORDER by "Start Date" asc * Thank you for the explanation on Baseline / Target. I will discuss with my PO.

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

RE: AUTOMATION: Updating Epic Dates based on Story Sprint Dates

Isabella Musial

I am trying to update the Epic Baseline Dates based on Sprint Dates of the Stories. For example:

If any story is moved into Sprint 1 (assuming Dates are added to Sprints), then the Baseline (or Target) Start on the parent Epic would update to the first day of the Sprint
If any story is moved into the last Sprint (assuming Dates are added to Sprints), then the Baseline (or Target) End on the parent Epic would update to the last day of the Sprint
If any stories are moved to later / earlier Sprints, the Epic would update accordingly

I have the Target Start / End dates updating on Stories based what Sprint they are moved to, but I cannot figure out how to update the Parent issue dates.

This is the closest example I can find: Jira automation template library | Atlassian

I hope that makes sense...

Thanks for your help in advance!

Accepted answers

All comments

Bill Sheboy

Hi @Isabella Musial

First thing, I am using Jira Cloud and not Jira Server, so my suggestions are based on what I know about automation rules, and not specifics for the Server version.

In your current rule, have you considered branching to the parent (after the story is updated) to make the change by comparing the date values currently in the epic, parent?

If that will not work...does your version of Jira Server automation have the Lookup Issues action? If so, you may want to take a look at that, using the min and max functions for a list to find the dates you need.

Kind regards,
Bill

Craig Nodwell_7eve9b

Hi @Isabella Musial I have to agree with @Bill Sheboy your best course of action here is to create a Branch Rule to handle updating the parent.

Isabella Musial

Thanks @Bill Sheboy & @Craig Nodwell for responding - really appreciate it!!!

So based on Jira automation template library | Atlassian, I created the following branch rule:

I exported my Automation Rule, but could not attach the JSON here unfortunately, It's a very long Automation Rule, so attaching Screenshots may be a bit difficult. I do think that the base Automation Rule I am using may be a bit over complicated!

Bill Sheboy

Does that rule work as you expect?

I suspect it does not: inside the branch, the edit issue's JSON is setting the dates based on fields in the {{issue}} and at that point in the rule, {{issue}} refers to the epic. (Context and scope are important in rules, and so where you are determines the value of {{issue}}.)

If your trigger issue is the one with the sprint values, please change the JSON to use {{triggerIssue}} rather than {{issue}} as the source of the fields to copy.

Isabella Musial

@Bill Sheboy @Craig Nodwell Unfortunately, still perplexed by this issue!

A coworker shared the following Automation with me:

Set Epic Start and Due Date to earliest/latest Chi... (atlassian.com)

@Trudy Claspill responded and offered a solution.

The concept is what I am looking for, however, this is using Start Dates.

I want to update the Baseline start / end based on the earliest/latest child dates. AND hoping that those dates update in Structure.

This is a 2-fer really...

Update Epic Baseline Dates based on earliest/latest Child Dates
Display those dates in Structure so that we can show if the schedule is slipping

I did create this Automation - but this will only run on new changes. (if it runs at all) I would love to run an update so that I can align all the past dates as well.

baseline automation.PNG

Bill Sheboy

Hi, Isabella.

For your version of Jira, do you have the Lookup Issues action for rules? I asked that earlier and perhaps it got lost in ideas.

If you have that action, you could:

use either a manual trigger (or scheduled trigger) to select the epics to update
use Lookup Issues with JQL to gather the child issues for each epic, and
then update the epic, as needed with the values
- earliest target start would be: {{lookupIssues.Target start.min}}
- latest target end would be: {{lookupIssues.Target end.max}}

Isabella Musial

@Bill Sheboy OH I like that!!! I'll try that to see if it can work.

Would I need to remove anything out of that current automation?

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server