Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,871
Community Members
 
Community Events
176
Community Groups

Associate custom sub task with a custom tasks

What is the reason do not have the possibility to have a few custom sub-tasks associated with custom tasks in one project?

Fo example:
On one project
Dev task -> dev sub-task (with dev workflow)
Design task -> design sub-tasks (with design workflow)

At this moment I get how to set only:

All tasks could have any type of sub-tasks

2 comments

That's correct, Jira does not have a function to limit sub-task types by the parent type.  

Like John Funk likes this

[Edited with working example. Also, the UX is not that bad.]

So, it turns out you can do this in Cloud with any of the add-ons that support Validators that allow for custom Jira Expressions. (Which is I think all of them.)

Basically I added a Custom/Scripted/Build-it-yourself Validator on the Create transition with the following Jira Expression:

(issue.issueType.name == "Sub-task" 
&& issue.parent.issueType.name == "Task") || 

(issue.issueType.name == "Bug Sub-task" 
&& issue.parent.issueType.name == "Bug") ||

!["Bug Sub-task","Sub-task"].includes(issue.issueType.name)

With an error message:

Only Tasks can have Sub-tasks. Bugs must have Bug Sub-tasks.

So basically what this is doing is, if the issueType of the issue you are trying to create is a Sub-task, the parent must be a Task. OR, if you're trying to create a Bug Sub-task, the parent must be a Bug. Lastly, if you are not trying to create either kind of Sub-task, then the validator lets you proceed.

Here's what it looks like if you don't match it up right:

subtasks.png

It's easy enough to flip the Issue Type and get it right.

Like Sergey Shkut likes this

Hm, it can help.

Thank you

Darryl Lee Community Leader May 28, 2021

Ooof, for some reason I was thinking of Jira Cloud. My bad.

Yeah, that add-on looks like it would do exactly what you need.

  • Restrict allowed parent issue types for subtasks.

In my example, it can't be done with two separate Validators, I forgot that unlike Conditions, you can't have "Any". I still think it can be done with a single Jira Expression. 

Anyways, apparently it can be done on Server/Data Center with:

Darryl Lee Community Leader May 28, 2021

But yeah, this can't be done out of the box:

https://jira.atlassian.com/browse/JRASERVER-7990

Thank you for your help.
These links are the next level of working with JIRA

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events