i tried "and sprint not in futureSprints()" but that doesn't work to exclude future sprints, looks like the function doesn't work properly unless i am missing something, or the definition of 'future sprint' is not what you and i think of what is future (i.e. everything that is neither current nor closed'
If you have only sprint per project the query below is nice:
sprint in openSprints()
But I have a project with multiple active sprints, how can I differentiate between those?
My goal is to create a filter that shows per sprint, the stories that we added after the sprint started.
What would be nice is something like:
sprint in openSprints('added stories') to show feature creep
sprint in openSprints('removed stories')
I want a data field that indicates an issue's current sprint association. Right now the "sprint" field contains every sprint an issue has ever been associated with. This makes sense for long term reporting but it makes it difficult to see which sprint an issue is in right now. The currentSprint() and openSprint() don't provide that information.
There seems to be a bit of confusion on the functionality of openSprint()
I think it's because the name suggests that it returns all sprints that are not closed whis includes future sprints. I was also confused by this.
This is NOT the case. From openSprint() documentation it clearly states: "Search for issues that are assigned to a sprint that was started, but has not yet been completed"
So in order to find tasks in the active sprint you only need to write "sprint in openSprints()" no need to exclude future sprints.
Remember: There can be many active sprints. Typically one per Scrum team. Hence you still need to include only the tasks that relates to your team.
An open Sprint is any Sprint that is not in a close status. We have several open Sprints because we are Product Roadmapping. I need a search function that only returns the current "Active" sprint that has been "started" and that we are current working in. Open Sprints returns too many issues.
Starting with the 7.2 Jira Agile REST API, you can set properties on sprints. Depending on what resources you have available to you, you could set an "active" property on the desired sprint and update as needed.
Not sure if you can use that in JQL yet like you can issue.property, but if you have ScriptRunner @Jamie Echlin might have a suggestion or two.
Hi Atlassian Community, We recently published a case study that we thought you might be interested in. Learn about how InVision built their fully remote company’s culture using Atlassian and Slack ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events