nadavspi/UnwiseConnect

Warn when selecting start date in the past on ticket dispatching

Opened this issue · 2 comments

gil-- commented

This should be relatively simple but show a red message that the selected start date is in the past. There are very few cases where you'd want to dispatch back in time. And I accidentally had the wrong date selcted and had to go through and delete a sprints worth of work. T_T

I agree on adding a warning label. Do you think it would be okay if we made it just that -- a warning? I have run into a few situations where I have wanted to go back and correct dispatch for days in the past. It's rare, and it should be rare, but it can happen. Among some other scenarios, there have been times on my teams where the dispatch ended up being planned incorrectly, or timelines changed last minute. Developers have alerted me to the problem, and I've gone back the next day to adjust it to allow them to have a dispatch that is more representative of the work I expected them to have completed. In that case, it also provides them with the opportunity to mark the correct tickets as done

gil-- commented

Yup, I agree it should still be allowed but some visualization such as a warning label would be sufficient to grab one's attention. We can just compare selected date to browser date and show.