Jira Structure: Displaying completed stories grouping by sprint shows duplicates for each sprint

[Peter McCann]

I would like to use the sum story points column to help show in one view the completed work across sprints. It can do this with a simple JQL query and a group by automation, except the data is skewed because using Sprint as the group by condition shows the story in both sprints it was in due to falling over from the initial sprint. 

I have an insert filtering by only stories with a status category of done, but still because the sprint field has multiple sprints in it, the structure shows them as aggregated point values for both sprints. 

Is there a way to tell the structure to only count stories in sprints where they were completed?

[Stepan Kholodov _ALM Works_]

Hello @Peter McCann 

Unfortunately, this is not possible - Story Points and Sprint are two separate independent fields in Jira, so there is no tracking of how many Story Points were completed in a certain Sprint. You can see a single existing number in the field and you can see the Sprint or Sprints where the issue was present.
In Structure, the aggregation considers the existing Story Points number as it is without splitting it into Sprints-related portions. Maybe you could look into using scripts or some other method where, for example, a certain number of Story Points would be set in a custom field once an issue's Sprint is being completed; in this case, you'd be able to calculate values in this field alone.

I hope this helps. If you need any assistance with Structure, please feel free to contact us directly at support.almworks.com

Best regards,
Stepan Kholodov
ALM Works

[Peter McCann]

I think your answer's focus was on the points. Instead my focus is on the inability to group by the sprint a given story was resolved in. 

Is there a way to group by stories where they only appear under the sprint if the story was resolved in that sprint? 

[Stepan Kholodov _ALM Works_]

@Peter McCann 

You can try to use this formula:
sprint.filter($.startDate < this.resolutionDate and (this.resolutionDate < $.endDate or !$.endDate))
It will compare an issue's Resolution date with the dates of its Sprints. All Sprints that began before the issue was resolved will be returned. If you don't set End Dates for Sprints, you can use completeDate in the formula instead which is the date when the Sprint was completed.

Best regards,
Stepan Kholodov
ALM Works