We are trying to find an "automated" way to stop a story from moving from one kanban status to another, until specific subtasks are completed. The real answer to this question would be to redesign the entire workflow and open and close stories at appropriate times but that will not happen in this situation. The situation is such that requires an automated gate to stop a story from moving from one status to another. Is that possible with Jira Automation rules? I have tried, and I haven't been able to figure it out with Jira automation. Please note, no third party gadgets allowed.