As already shared by @Alana Fernando, it's not possible out of the box in JIRA to see the stories burned per sprint of an board/project in a single chart of JQL. Because in JQL you can use the query like "Sprint in (X,Y,Z))" to get the issues from all sprints, but categorizing per sprint is not possible, also lot of issues have multiple "sprint" values in JIRA because an issue might have worked upon in sprint 1,2,3 but closed in sprint 4 thus using JQL you might not get correct results.
I have been able to create chart which shows velocity per sprint of an project/board using the combination of script runner and dataplane plugin. Here's the description as to how to achieve it.
As a workaround to the above suggestion (because I can't do an add-on for $120 a month just to get the individual velocity calculated, the velocity chart within the project is very helpful. If you click on the Sprint it opens up the Sprint Report, The list of "Completed items" has a link to the far right that says "View issue in Navigator". Click on that and it takes you to the filters page where you can configure the layout how you need it. If your team is documenting story points religiously, then you can total them up per Engineer from each individual Sprint velocity list. Hope this helps. :)
it is not possible to filter out sprint names , and total closed stories per sprint in Advance search of default JIRA. instead you can search for closed stories per sprint and get the total value one sprint at a time.
try below JQL.
Sprint = <sprint ID> AND type = Story AND status = Closed
Other than that, you may export the closed stories to excel and filer out the results by sprint.
Hello @Alana Fernando
Above JQL would give inconsistent results because if an issue is closed in sprint 4 and now closed but was worked upon in sprint 3 as well thus in JQL if we use JQL "Sprint = Sprint 3" then we might get issues which were worked in sprint 4 and are now closed but were worked upon in sprint 3(as sprint field supports multiple values in JIRA). And we don't want that as we want only the issues which were exclusively closed only in sprint 3.
I have shared in the below answer as to how it can be achieved.
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