How to block the creation of subtasks in tasks
Making it available only for stories
Without the use of external plugins, it can be done via workflow.
Hello Lucas,
Welcome to the community..!
Please check this KB if this helps.
Otherwise, as @Trudy Claspill mentioned, use Automation to delete them once created.
Set the Trigger:
Choose the Issue Created trigger.
Add Condition:
Add a condition Issue Fields Condition
Field: Issue Type
Condition: equals
Value: Sub-task (or whatever your subtask issue type is named)
Add Action to Delete the Subtask:
Add an action to Delete Issue.
Please note: Deleted work items are gone forever.
When a work item is deleted all of its data, including comments and attachments, can't be restored.
Regards
Harpreet Walia
I think you can use Workflow Conditions to restrict sub-task creation
Jira allows you to control which issue types can create subtasks by configuring the workflow transitions for sub-task creation.
Go to Project Settings → Workflows.
Find the workflow used by your sub-task issue type.
Edit the workflow.
Click on the “Create” transition for the sub-task workflow.
Add a “Condition”:
Choose “Parent Issue Type” condition.
Configure it so that the parent issue type must be “Story”.
This means subtasks can only be created if the parent is a Story.
Publish the workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @yqiao
I believe your answer is incorrect.
The Create transition in a workflow is special. It does not support Conditions. It supports only Validators and Post Functions.
Additionally there is no such condition as "Parent Issue Type" provided natively by Jira Cloud.
If you are able to create this configuration in a Jira Cloud environment can you provide a screen image?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @lucas_morais
Without the addition of third party apps there is no method through workflow customization to block the creation of sub only work around to prevent creation of subtasks under one type of issue in a project while allowing them to be created under another type of issue in the same project.
The only workaround available is to use an Automation rule to detect that they have been created and then have the rule transition them to closed or delete them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.