Allow assigned comments to block a specific status change, not just task closure
Amara Amzal
Request:
Right now, an unresolved assigned comment only blocks closing the task. In practice that's often too late: the issue needs to be fixed before the task moves to a specific stage (for example "Client review" or "Ready to print"), not at the very end.
I'd like an option, when creating or assigning a comment, to choose which status it blocks. As long as the comment isn't resolved, the task can't move to that status (or any status after it).
Why automations don't work here:
these blockers are contextual and decided case by case (a missing file, a client validation, a correction to check). You can't predict them with rules or required fields, and they belong in the conversation where the problem was raised.Expected behavior:
- A "Blocks status: [X]" selector on assigned comments
- A clear message when someone tries to move the task past that status, with a link to the blocking comment
- The block is lifted automatically once the comment is resolved
Log In