Description -
Per Workfront Support > "For Kanban, tasks from "On Hold" projects typically remain visible on the board because Kanban focuses on continuous delivery and flow. However, for Scrum, tasks do disappear, as Scrum works in fixed sprints, and to maintain workflow, non-active tasks should not be displayed."
The reasoning for the difference in functionality does not make sense. You can not focus on continuous delivery and flow is you cannot work on the card when a project is on hold. The system prevents you from updating the card, and rightly so. The Kanban board should not display work that cannot be worked on.
Why is this feature important to you -
The current behavior is confusing and keeps the board cluttered with work that cannot be worked on. Unlike the Scrum team where Tasks in an On Hold project drop off the backlog and sprints.
How would you like the feature to work -
The functionality should mimic the Scrum setup. If a project is on hold, then the cards should drop off the Kanban backlog or the board if already put on the board. Tasks that cannot be worked on should not show.
Current Behaviour -
If you have a card on your Kanban Board and the project is put On Hold, the card becomes stuck on your board. You cannot update the status, progress, or assignments because it the source project is on Hold.
