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

How extract the startDate and endDate of a future Sprint?

Doug Levitt_tunij3

Hi Automation for Jira Experts,

A colleague of mine -- using the Jira API -- has created a number of future Sprints, setting the startDate and endDate.

Then, after an issue is added to a future Sprint, I want to set 2 custom fields -- PlannedStartDate and PlannedEndDate based upon the startDate and endDate of that future Sprint.

This is easy to do, when an issue is assigned to only 1 Sprint. However, occasionally some of our issues are associated with one or more previously closed Sprints (as the team didn't finish the work in the originally planned Sprint).

As an example, below is the JSON from such an issue:

"customfield_10006": [
{
"id": 2579,
"name": "AgileExample 149 (ends 7/27)",
"state": "future",
"boardId": 260,
"goal": "",
"startDate": "2021-01-01T00:00:00.000Z",
"endDate": "2021-01-02T00:00:00.000Z"
},
{
"id": 2246,
"name": "AgileTest 2",
"state": "closed",
"boardId": 260,
"goal": "",
"startDate": "2021-01-03T20:14:00.000Z",
"endDate": "2021-01-17T20:14:00.000Z",
"completeDate": "2021-01-26T18:38:47.127Z"
},
{
"id": 2278,
"name": "Snoopy 242 (ends 1/17)",
"state": "closed",
"boardId": 260,
"goal": "This is the sprint goal...",
"startDate": "2024-01-03T20:00:00.000Z",
"endDate": "2024-01-17T20:00:00.000Z",
"completeDate": "2021-01-30T00:23:16.746Z"
}
],

Things would be simple if the "future" sprint was always the first in the list (or the last in the list). As then I could use list.first or list.last function as described here <link>.

However, after some testing, I realized that there is no guarantee where the "future" Sprint will occur (and hence I don't know which element in the list to pull the startDate and endDate).

Question - Is there a way to "walk" the JSON object, looking for the startDate and endDate matching the element where state = "future"?

Thanks!

Doug

Accepted answers

All comments

Darryl Lee

Huh.

I was reading "How can I iterate through a multi-select field in an Automation for Jira flow?" and thought, huh, would there be a way to keep "popping" sprints off of a copy of the "stack" until you hit the one with future?

Like say you assigned {{checksprint}} to {{customfield_10006}}

And initialized {{futuresprintid}} to ""

Then did something like:

IF {{check.first.state}}="future" block...

THEN set {{futuresprintid}} to {{check.first.id}}

ELSE

Advanced Edit, and remove the *first* element from {{checksprint}}, using the the "update -> remove" function?

---

The thing is, I think this will only run once, as there's no outer WHILE check.first.state !="future" loop or anything like that.

I guess you could code it as a series of ELSE-IFs for the maximum number of Sprints you think users might select for an issue?

It's ugly, but hey, that's what I do. :-}

Darryl Lee

The original poster wrote:

You can use "re-fetch issue data" and continue the rule if there are more "Teams".

The other option is to change a different field so it will run a different automation rule as long as "Teams" is not empty.

Hrm. I kind of don't think re-fetch issue data is going to refresh a smart value variable.

But maybe the idea of using a different field to store the temp value would work.

Sorry, have some other stuff to play with today so I can't test this out for ya.

Doug Levitt_tunij3

@Darryl Lee Thanks for your response. I am somewhat surprised they didn't provide a way to interrogate a list structure (to find a particular entry in the list).

Darryl Lee

Hey yeah, it'd be nice if there was a method to filter or select.

Oh look, there's bugs filed for this:

https://codebarrel.atlassian.net/browse/AUT-1241

https://jira.atlassian.com/browse/JRACLOUD-76040

Bill Sheboy

Hi @Doug Levitt

What do you plan to do with PlannedStartDate and PlannedEndDate, and when do you plan to use that information (relative to the sprint start timeframe)?

For example, if you do not plan to do anything until after the sprint starts/completes, you could just set the values based on the trigger Sprint Started.

However, if you want the information before the sprint runs, you definitely need to get the data from the REST API. The sprint startDate and endDate do not appear to be available in the smart values within automation rules until the sprint begins.

Perhaps instead you are calling the REST API with a webrequest from within a rule...Once you have the complete sprit information, you could probably use match() and RegEx to pull out the Future state sprints.

Best regards,

Bill

Doug Levitt_tunij3

I plan to render the dates in Advanced Roadmaps.

I am planning to set the Adv Roadmaps Start Date to the date a Story went in progress, if set. Otherwise, I will set to Planned Start Date.

I am planning to set the Adv Roadmaps End Date to the date a Story is marked done, if set. Otherwise, I will set to Planned End Date.

As a note, I have implemented a "sort of" solution. It's kind of a hack. I am setting Planned Start date to: {{issue.customfield_10006.startDate.max}} and Planned End date to: {{issue.customfield_10006.endDate.max}} - Basically, I am assuming that the closed sprints have an earlier date (than an open or future sprint). Generally speaking that should be the case.

Darryl Lee

Oh that's a good hack. Glad you figured out out.

Dave

Hi @Doug Levitt ,

I'm on the Advanced Roadmaps team and I'd to understand your use case for this feature further. Something that I've been keen for us to add to Advanced Roadmaps is to have an additional bar on the timeline to show when issues transitioned into and out of an "In Progress" workflow states (the idea being that you'd be able to compare when you planned work to happen with when it actually happened). It sounds like this is sort of what you're trying to do here? (except you're going to capture the actual dates to replace the planned dates). I'd love to understand further about why you want to do this.

Also, additionally I just wanted to check that you were aware that there is a configuration setting on Advanced Roadmap plans that allows the roadmap to show the start and end dates of issues based on the sprints that they were assigned to. I thought that was worth mentioning because it also sounds somewhat related.

Regards,
Dave

Welcome!

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

Quick Links

Find more posts tagged with

automation