Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to configure subtask types for specific Issue Types

Olivia Medina January 24, 2025

Hi guys, 

I have a Jira Project with different issue types (e.g. Scoping, Planning, etc) I need to be able to create subtasks for each of these issue types (e.g. Scoping Subtask, Planning Subtasks...) but I need to restrict the creation of these subtasks per issue type so I don´t allow users to create a subtask linked to the wrong issue type.

I´m thinking of including automation to check the parent issue type and make the switch to the correct one if the subtasks do not correspond to that issue type. But I would also like to create maybe a validation so from the very creation this problem is solved. Any ideas?

I really appreciate any help you can provide.

1 answer

0 votes
Valerie Knapp
Community Champion
January 24, 2025

Hi @Olivia Medina , welcome to the Atlassian Community and thanks for your post. 

Is there any particular reason why you have to have different subtask types for each standard issue type? Or could you just use the same subtask type and avoid to have to do this configuration?

Best wishes 

Olivia Medina January 24, 2025

Hi @Valerie Knapp thank you! And yes, there is a particular reason for this project, each issue type has a specific workflow that is shared with the related subtasks.     

Valerie Knapp
Community Champion
January 24, 2025

Hi @Olivia Medina , thanks for clarifying. My recommendation would be, wherever possible, to automate the creation of the subtasks to avoid the problem of the wrong ones being created. 

https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/1363678 

Please check out this rule for example. 

What you are proposing, to have some validation on the parent to determine what child is correct is likely more feasible with an app, like ScriptRunner or Jira Misc Advanced Workflows. Do you have any apps to help you achieve this? 

Best wishes

Olivia Medina January 27, 2025

Hi @Valerie Knapp , 

Thank you for your assistance on this one. I'm checking the automation rule to see if it's feasible as the logic implies switching to another issue type if created incorrectly. Still, as I have different workflows per issue type, I might find an issue with the automation when two different workflow statuses must be replaced.

Thank you for the one you sent me, I need this as well as I'm creating a template board to reuse on recurrent projects with the same repetitive tasks. 

Kind regards,

Olivia Medina January 29, 2025

HI @Valerie Knapp , 

As mentioned, the automation only works when the issue types have the same workflow. Otherwise, you get a warning, and the rule won´t work. I will need to rethink the logic here and maybe use the automation you suggest to autogenerate the subtasks based on the parent. 

Thank you,

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events