Feature Category
None
Problem Statement
TaskNotes enforces a strictly linear status flow. When the list rolls over, every state advances to the next one—even if that logic doesn’t match real-world workflows. For instance, a task marked Blocked should progress to Complete once the blocker is resolved, but instead it cycles back to Backlog because Blocked happens to be the last status in the list.
Proposed Solution
Allow users to define explicit “next-status” mappings for each state. If a mapping exists, the plugin uses it; otherwise it falls back to the current linear order. This supports many-to-one transitions (e.g., both Blocked and In Progress → Complete)
Use Case Examples
Blocked → Complete → Archive
A task stalls in Blocked. When unblocked, a single keypress moves it straight to Complete, then on the next advance to Archive.
In Progress → Complete
Active work finishes; advancing status marks it Complete without stepping through irrelevant states.
QA Failed → In Progress
Custom mapping sends failed QA back to In Progress, bypassing intermediate statuses that don’t apply to rework.
Priority/Impact
Medium - This would be a nice improvement
Additional Context
Easy workaround is to right click on status to select next status. This is a nice to have, but note that this is the behavior of Task plugin.
Feature Category
None
Problem Statement
TaskNotes enforces a strictly linear status flow. When the list rolls over, every state advances to the next one—even if that logic doesn’t match real-world workflows. For instance, a task marked Blocked should progress to Complete once the blocker is resolved, but instead it cycles back to Backlog because Blocked happens to be the last status in the list.
Proposed Solution
Allow users to define explicit “next-status” mappings for each state. If a mapping exists, the plugin uses it; otherwise it falls back to the current linear order. This supports many-to-one transitions (e.g., both Blocked and In Progress → Complete)
Use Case Examples
Blocked → Complete → Archive
A task stalls in Blocked. When unblocked, a single keypress moves it straight to Complete, then on the next advance to Archive.
In Progress → Complete
Active work finishes; advancing status marks it Complete without stepping through irrelevant states.
QA Failed → In Progress
Custom mapping sends failed QA back to In Progress, bypassing intermediate statuses that don’t apply to rework.
Priority/Impact
Medium - This would be a nice improvement
Additional Context
Easy workaround is to right click on status to select next status. This is a nice to have, but note that this is the behavior of Task plugin.