Prevent user from adding multiple sprints to a Issue

Question

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.?

Bill Sheboy · Answer

Hi @Arun Unnikrishnan

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.

Kind regards,
Bill

Fabio Racobaldo _Catworkx_ · Answer

Hey @Arun Unnikrishnan ,

it can happen because a task could be not completed in a closed sprint and be in the next one. You can not place a ticket in a current and future sprint.

Fabio

Arun Unnikrishnan_ul3s5t · Answer

Thanks @Fabio Racobaldo _Catworkx_

This one - for example - is in already completed Sprint and Current Sprint.