You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a busy user
I want to be able to see at a glance whether I have an active timer and which one it is
So that I can remember to stop my timers #221 and can do so without having to spend 2 minutes looking for the active timer.
Acceptance criteria
Timer line item bubbles to the top of the timer list when activated
There is an open question for me here on whether the timer should return to its original position once stopped.
I think yes, because once there is a prioritisation feature #283 because we don't want to mess with people's prioritised lists.
I will however, open a separate issue on this as I think it's lower priority for now.
I'm only mentioning it because it may inform the technical implementation (passing parameters of the original 'location' for example).
The text was updated successfully, but these errors were encountered:
Note: This would be a useful feature soon because with all the tag colours and the different colours in the timer column (2 shades of turquoise for Start and Resume, Save in green and Stop in red plus the logout button also in red in the same visual column) I'm finding this task particularly onerous. Particularly in the absence of the ability to move tasks around myself.
@iteles totally agree this is a super useful feature in even a modestly sized list! 🔝
Would you want this feature to be configurable? 🔧
i.e: people can enable it if they want it and disable it if they don't? ✅
As a busy user
I want to be able to see at a glance whether I have an active timer and which one it is
So that I can remember to stop my timers #221 and can do so without having to spend 2 minutes looking for the active timer.
Acceptance criteria
There is an open question for me here on whether the timer should return to its original position once stopped.
I think yes, because once there is a prioritisation feature #283 because we don't want to mess with people's prioritised lists.
I will however, open a separate issue on this as I think it's lower priority for now.
I'm only mentioning it because it may inform the technical implementation (passing parameters of the original 'location' for example).
The text was updated successfully, but these errors were encountered: