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
We have cases where users (the assignee) adding the issue to a Sprint 1. But say the Issue is not resolved in Sprint 1, so the assignee just adds Sprint 2 to the issue. Now the Issue has two sprint to it - Sprint 1 and Sprint 2.
I have fixed this with bulk update. Educated the team on best practices but still want to check -
Is there any way we can restrict the users from adding multiple sprints to a issue? Can be a error message, can be a automation which would send an email to Mr. X saying that your good friend has added multiple sprints to same issue.?
Adding to Fabio's answer:
I would not recommend removing the prior sprint(s) when an issue is carried over; that is, not completed in one sprint and so continues in another.
That would change the history of what happened, and takes away an opportunity for the team to consider what happened, learn from symptom, and decide how to experiment to improve in the future.