nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Restrict the creation of subtasks by the type of the parent ticket

Manar El Kefi

Hello, I want to restrict the creation of subtasks by the type of the parent ticket. For example, I don't want a story type parent ticket to have a subtask. How can I do this using automation?

Accepted answers

All comments

Hans Polder_7ci2ta

HI @Manar El Kefi ,

Why would you want to use Automation for this? Could you share a bit more context about the use case/situation you want to solve?

Please keep in mind that natively in Jira this is not supported: https://jira.atlassian.com/browse/JRACLOUD-7990

Annie@DevSamurai

Hi @Manar El Kefi

To restrict the creation of subtasks based on the parent ticket type, you can follow the automation rule below on how to set it up.

Navigate to Automation:
- Go to your Jira project.
- Click on Project Settings in the sidebar.
- Select Automation from the settings menu.
Create a New Rule:
- Click on Create Rule.
- Choose the Issue Created trigger. This sets the rule to activate whenever a new issue, including subtasks, is created.
Add a Condition:
- Click on New condition.
- Select Issue fields condition.
- Configure the condition:
  - Field: Issue Type
  - Condition: equals
  - Value: Sub-task (or the specific name of your subtask type)
Branch Rule/Related Issues:
- Click on New branch.
- Select Parent. This creates a branch that allows you to evaluate the parent issue of the subtask.
Add Another Condition:
- Within the parent branch, click on New condition.
- Choose Issue fields condition.
- Set the condition:
  - Field: Issue Type
  - Condition: equals
  - Value: Story (or the specific issue type you want to restrict)
Add an Action:
- Click on New Action.
- Choose one of the following actions based on your requirements:
  - Delete Issue: This action will delete the subtask if it meets the conditions.
  - Send Email: To notify users via email.
  - Send Slack Message: To notify users via Slack. You will need to configure the message and provide a Slack webhook URL.
Save and Enable the Rule:
- Once you have configured all the components, click on Save to save your rule.
- Ensure the rule is enabled by toggling the switch if needed.

Here is the automation flow that I set up based on your requirements above:

I hope this may help!

Annie

Annie@DevSamurai

To test the rule, you can create a Story issue and create a subtask under it. Then you can see the subtask is automatically deleted.

Manar El Kefi

Annie@DevSamurai I did the same steps but when I create for example a subtask for a task parent , it's created. I don't know why

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud