Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Rich Filters (Addon) - Story points counted on multiple sprints

dbaumann
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 4, 2022

Im using the Rich Filter Statistics gadget to create a 1 year velocity chart for a project.

However, it seems if a ticket gets carried over to a second sprint (or gets pulled from a sprint and added to another later), its story points get counted toward both sprints, artificially inflating how many completed points are counted toward each sprint.

 

Is there a JQL query I can integrate into the  setup of the Rich Filter Statistics gadget to prevent this?

 

Also, on this same gadget, my sprints are in either Alphabetical order, or Total order.  Is there a way to sort by sprint date?

 

 

2 answers

0 votes
Stu Shapiro
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 16, 2025

Hi @dbaumann ,

I know your post was a while ago, Im having the same issue, did you find a solution ?

Jean-PierredeTiege
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 20, 2025

Put in a column like ResolvedInSprint as a Jira Field (number) and fill it with the value of the sprint the work item was actually transitioned to Done. Optionally also create a ResolvedInSprintByName value to put in the name of the sprint.

Set up an automation rule that fills these values for current/upcoming stories there where they haven't yet transitioned to done. Use Power Script to process historical issues by looping through a list of work items and for each work item loop through the list of sprints it's associated with. for each sprint, check the start and complete date and see whether the resolution change date falls inbetween these two sprint dates. If so, set the required values on the fields.

Optionally ensure you've got the earliest possible resolution to done change get all the changes on the status field and loop through them; this to cover off stories that were set to done multiple times. 

This doesn't cover all scenarios but should set you up for ensuring you get exact figures when it comes to understanding which work item was finished in which sprint there where a story spanned multiple sprints. 

0 votes
Fabian Lim
Community Champion
November 5, 2022

Hi @dbaumann

Welcome to the community!

We use rich filters a lot but for sprint velocity is not the best option.  I suggest you consider other plugins from the marketplace. 

Regards 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events