Hello All,
I am looking for some help on how to write a JQL query that includes data from the last 5 or so sprints. The number of sprints looking backwards can be flexible, but I am hoping to find a way to use the "closedSprint()" value to only look at a few sprints back.
Any recommendations?
Hello @Riley Piper ,
If you are considering using the application for this task, you can probably check Power Scripts for Jira. Using its JQL functionality, it is possible to establish JQL custom keywords that are associated with a custom script. This allows for the implementation of any required logic within the script.
If you are interested, please visit these pages for more details: JQL Support, Custom Keywords, and also adding a link to the list of sprint-related functions that can be used for script creation Sprint Functions.
In case you try this approach but face any issues or questions, feel free to create a support request here and share more details about your particular use case.
Hope it helps!
Anna
Hi @Riley Piper
What data do you want to see from the JQL?
For example is it anything which was in the last 3 sprints? Or just issues closed within that timeframe? Or...?
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Inactive Stephen
I am looking for a way to look back on completed issues the last 3 sprints. The purpose of that dynamic field is really just so we do not have to go in and manually update the sprints in the filter at the close/start of each sprint.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Riley Piper - Unfortunately, this is not possible with native Jira functionality and I'm not even sure that it's possible with a marketplace app. It would likely require some form of scripting leveraging the API to pull that information.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I appreciate the quick response here Mark! Not a big impact for us as it was more of a nice to have.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.