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,463,681
Community Members
 
Community Events
176
Community Groups

Can I create a Custom Jira Type that is the Child of another Custom Jira Type

I am trying to create two (2) different Custom Jira Types where one type is the "Parent" and the other is the Child.  In other words one Parent record can be linked to zero-to-many Child records.

Is this relationship possible?  Can this be accomplished with existing Jira Linking functionality?  Does it require an Administrator to establish the "Parent-Child Nature" of that relationship?

Thanks in advance for your feedback on this matter.

2 answers

1 accepted

1 vote
Answer accepted
Craig Nodwell Community Leader Mar 21, 2022

You could achieve this through creating a Standard Issue Type and a Sub-Task Issue Type then applying the appropriate schemes and contexts to the project(s) you wish to apply them too.  By creating the standard/sub-task issue type when they are linked an automatic parent child relationship linking is created.  You could of course further enhance this through customizations, but keep in mind these always come with some maintenance overhead considerations.

Understanding Issue Types in Jira 

I hope this gets you started.

Thank you very much Craig Nodwell.  This is precisely the type of response I was expecting.  I suspected that Jira would have this type of functionality natively out-of-the-box.  Thanks for confirming the same.

Rolland

Craig Nodwell Community Leader Mar 21, 2022

Hey, you're welcome.
I've been working with Atlassian since Jira version 3, `17 years (my current community status doesn't reflect this so much due to being a consultant).

My experience isn't the point, the point is the experience I've gained via the community.
I've found that the community and technical support surrounding these tools has always been strong, friendly, and insightful. 

It is mostly for this reason I try to stay involved.

Hope you enjoy finding, and realizing the solutions to your business/development needs.

1 vote

Hi Roland,

There is also a 3rd part app called Structure for Jira that can be used in order to define any parent-child hierarchy, with any number of levels, you wish using Issue Links.

If you are already using Advanced Roadmaps for Jira you may notice Roadmaps supports the usual Jira 3-level hierarchy: Epic > Story > Subtask. You may be able to modify the hierarchy to suit your parent-child needs in this instance. Please refer to link provided for more info.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events