Can we prevent Sub-tasks to be created on a Story that has been already completed for weeks, months, etc.
I have had users take a done Story/Bug and add a new sub-task and work the ticket, the issue i am running into is some of the automations are not running because the ticket is completed for the story but the sub-task is open.
Hi @Becky Murray - Hope you are doing well. I think this is doable by adding a "validator" on the "Create" transition of the Subtask WF. Here is how you would do it -
Just make sure "Done" is not part of the parent status validator and all the status from where you want the subtask to be created is part of it. This will only work when they are creating a subtask directly under a parent.
I hope this will solve your problem. Please let me know if you have any concerns.
Thanks,
Bharat
Hello @Becky Murray
Based on my understanding, preventing sub-tasks from being created on completed stories is achievable through workflow conditions or validators.
You could implement an automation rule or a workflow transition property that restricts sub-task creation for issues in a "Done" status.
This ensures stories marked as "Done" remain static unless explicitly reopened.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join us to learn how your team can stay fully engaged in meetings without worrying about writing everything down. Dive into Loom's newest feature, Loom AI for meetings, which automatically takes notes and tracks action items.
Register today!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.