Closed tuna-salad closed 11 years ago
We definitely should inform the users that setting the estimate to 0 will send it to the backlog in some way.
made the status message say "A requirement must have a positive estimate to be assigned to an iteration" when an estimate is 0 and there is an iteration assaigned
What should happen if the user tries to save such a requirement? What happens now for our project is that the iteration will automatically be reset to "Backlog" after saving, although the iteration (that is changed to Backlog) is not updated to the model (actually a bug).
What about informing the users to reset the iteration themselves before attempting to setting the estimate to 0 again?