This idea has been merged into another idea. To comment or vote on this idea, please visit APP-I-1477 In workflows, it should not be possible to skip a certain status..
Similar to JIRA and other tools, would like to see the ability to configure validations to help enforce proper workflow. First, enforce flow from one status to the next and not ad-hoc. Secondly, have the ability to make certain fields required in order to advance to the next status. For example: Functional Acceptance Criteria cannot be NULL when setting status to 'Ready for Estimation'.
Without workflow validations, users are able to skip statuses and advance features to a status before they are truly ready. Without some kind of governance, the workflow is less powerful.
|Release time frame|
Within each status/workflow, we provide the ability to include different Transition buttons for each status. Many of our customers use the Transition buttons as a way to enforce workflow from one status to the next. You could encourage your team to solely use the Transition button as a way to move the feature through the workflow (as opposed to using the dropdown).
You can find these customizations via Account -> Configure status, workflows.
At this time, we do not have plans for updates in this area in the short term but we hope that this workaround can be helpful to you.