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

function in jql for previous sprint

Sameer Bansal_59tr81

Hi Team,

Need to get a function in JIRA for getting the last closed sprint which should be OpenSprint()-1, can you share the details for this.

Don't want to use script runner or any other plugin for this

Accepted answers

All comments

Jack Brickey

Hi @Sameer Bansal , unfortunately there while there is a closed sprints function there isn’t a “previousSprint” function. Obviously you can find previous sprint details in Reports. Is there some specific goal you are aiming for?

Sameer Bansal_59tr81

@Jack Brickey Actually i have created a dashboard wherein we want to compare the current sprint and previous sprint for management reporting. Right now it's a pain to change the previous sprint number everytime and if someone miss to update that then complete report doesn't make any sense

Jack Brickey

That is what I thought you might be attempting. Actually did you try this…

Sprint in openSprints(-1)

I don’t currently have any open sprints to verify this but a quick test says it might work.

Sameer Bansal_59tr81

@Jack Brickey - yes, openSprints(-1) doesnt do anything just shows open sprint adding -1 or anything in the brackets doesn't seem to work. maybe its a bug or i don't know

Bill Sheboy

Hi @Sameer Bansal

Yes, and...to what Jack notes: there is nothing built-in to do this yet.

As a work-around, you could use the built-in automation rule features to help in a few ways:

Use an automation rule which automatically updates your dashboard filter (using the REST API) when a sprint completes, shifting the filter to use the new "previous" sprint id
Or, add custom fields and devise a mechanism where you can distinguish the current and previous sprint, and set the custom fields with an automation rule. Your filters could then remain stable to support reporting/dashboards

Best regards,
Bill

Sameer Bansal_59tr81

@Bill Sheboy -

1) for REST API an not sure what will be the trigger point for the automation rule

2) for option 2 the requirement is to distinguish the current and previous sprint

i am checking if i can device a formula where i can subtract the name of sprint by 1
- example Current sprint name is "ABC 2" so somehow i can do "ABC 2-"1" " or something like that

Bill Sheboy

For option 1, you could trigger the rule on sprint completed.

Curt Holley

Further to @Bill Sheboy suggestions, if you are happy to receive whatever info it is you are after via email (from an automation rule), I've just got this working to report on the mentioned issue types in the JQL for the sprint that triggered the rule to run, by using the {{sprint.id}} smart value in the JQL.

Screenshot 2022-06-02 124549.png

Sameer Bansal_59tr81

it didnt worked, so i discarded the idea will check in future if reqired

Daniel Martin_sxbg92

I was able to achieve previous sprint using the following:

fixVersion in unreleasedVersions() and project = [YOUR_PROJECT_NAME] and fixVersion in releaseDate("after now() before 30d")

Bill Sheboy

Hi @Daniel Martin -- Welcome to the Atlassian Community!

I do not see the releaseDate() in out-of-the-box JQL functions. Are you using a marketplace addon to provide that feature?

Kind regards,
Bill

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

atl-gruland