Velocity charts shows different sprints

[Madhura Perera]

Hi,

We run multiple JIRA projects parallel to deliver different releases (e.g: Nov - Release 9, Dec - Release 10) to the customer as we have a big team of 100 ppl. 

Each project has it's own JIRA board, stories and releases (e.g: Release 9.1, Release 9.2). Depend on the customer priority, stories may move from one project board to another project board (e.g: Release 9 to Release 10).

But when I generate the velocity chart for one project, I see sprints from other projects as well. For an example, as attached picture 'Release 9 - Sprint 5' and 'Release 9 - Sprint 7' are appeared on the Release 10 velocity chart.

1. Any reason for this

2. How to remove this or prevent this

Cheers,

Madhura

[Nic Brough -Adaptavist-]

Sprints from one board will "leak" into other boards if the boards might have shared issues.  This is usually when you've got board filters that allow crossover (like "project = x or label =y" and "project = z or label =y"), but can also happen if issues are added to a sprint and then moved to another project.

[Madhura Perera]

Moving stories from one sprint to another or project is quiet normal in our project. We plan our next sprint during the current sprint but customer can change the priorities last minute. As a result, we have to move some stories to future sprints or another release (separate project). 

But when we move a story from one project to another project, it's treated as a completely new story and should not have any relation to the project it has been moved from. Is there a way we can do that ?

[Nic Brough -Adaptavist-]

There's the answer then - you've included issues that were in those sprints.

If you're moving issues from one project to another, it is not a new story, it's something that was in a different project.  If you genuinely need it to be a new story, then create a new one (and close the old one)