The “Complete task” shortcut (⌘ + return / Ctrl + return) is something myself and clients use quite frequently, and we love it.
However, with the introduction of Custom Task types, it’d be nice if the “Complete task” shortcut became more of a “Advance to next status” shortcut based on that custom task types custom statuses.
Ultimately, I’d really just like a way to set the custom task status using the keyboard. If you folks gave us a shortcut that would set focus on the .CustomStatusButton-button element, that’d work with me. I could then just hit return, arrow keys, then return again to change the status.
For example, suppose you have the following custom statuses for a custom task type named Work Item:
Triage
Backlog
Commit
Working
Complete
Closed
Hitting ⌘ + return would set an item with a custom status of Backlog to a status of Commit, instead of marking it Complete.
If it’s prudent to retain the Complete task functionality as it is, then it could be set to a shortcut of ⌘ + Shift + return.
Doing so would allow standard tasks that do not have a custom task status to still get marked complete with as usual, while simultaneously enabling sequential progression logic for custom task types.
I voted for the logic update, but I think I’d prefer this:
Existing ⌘ + return stays the same for regular tasks, but for a custom task type, it changes to the only completion status if just one completion status, or otherwise offers a popup choice of just the completion statuses
New ⌘ + Shift + return always offers a popup choice of all statuses.
I just want an easy way to advance to the next sequential status via the keyboard. If that means a two or three-step keyboard combo like ⌘ + return → down arrow → return, that’s fine by me.
And for what it’s worth, I can more or less do this now in some workflows. Tab sets the focus on the task status button when you open the task details pane—but it’d be nice to have a command that automatically focused that button without having to build a custom macro or something.
If there are status choices, they could be navigated with simple up/down arrow keypresses and chosen with return, without requiring the mouse, even in this more involved interaction.