You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We break projects out by teams and they have their own backlogs and srum boards. Team A has their their Scrum Board filter pulling in their teams work as well as work assigned to their workgroup from a "Service Request" project that many teams have work assigned to them from. All teams that are showing on the velocity report have unique sprint names.
On the velocity report it shows other teams that Team A, because they don't have enough work to keep them busy, will take on other work from those "other" teams. A story may be in one of the "other" team's sprint, but then Team A will reassign to their workgroup and move it to their sprint.
Is this issue happening because they reassign to the new workgroup and sprint without removing it from the "Other" teams sprint first before reassigning to their sprint?
JIRA Software version 7.1.6-Server Version