Does JIRA support the concept of sub-projects

I have a project that I'd like to break up into sub-projects. Is this possible in JIRA?

3 answers

1 accepted

3 votes

Not really. A project is pretty much the fundamental unit for groups of issues. You can use categories to do some division work (these work in filters, so you can say "category = X" and find several cross-project issues)

If you need something more detailed, have a look at the structure plugin - it's aimed more at issues, but seems to solve all the "project of project" problems that can't be done with simple categories too.

We have added sub-projects support to our "Component/Bundle/Subcomponent Version" add-on. It allows JIRA administrators to create hierarchy of projects using either virtual or real projects and adds a subproject picker to issue create screen. You can query issues belonging any level inside the hierarchy using "project in subprojectsOf()" JQL function. Please check user manual for more details.


It dosen't. But you can use "components" field as subprojects. In components we have entered all out subprojects and made that mandatory field for that specific project while creating an issue. Once this is done, its easy to create filters based on componends and feed them to the widgets onto your dashboard.


I tried checking this and edit the components field in a story in order to categorize the story into a sub-project but i am not able to edit the component field. Is this becasue i do no have the necessary permissions or because i first need to install a plugin?

Have you (as a project admin) added any components to the project yet?

Ok, can you explain "not able to edit" please?  What are the exact symptoms?

I am not a project admin so not able to add components. However, for that does the project admin have to install a plug in first? Is it free or paid?

Probably no components are added yet, that's why I am not able to edit the component attribute in a story.

I also want to explain my requirement here to check whether there are alternate solutions. We have multiple region specific projects running for a single product. But now we want to get all these projects under a single product umbrella. For that we created a master project and want tag each of the projects as sub projects under the master but I have read there is no parent-child relationship in projects in enterprise Jira.

So the option now is to move every issue from these projects into the master project manually and then categoize them using either labels or components. I think this will be time taking as I don't see an option to move issues in bulk from one project to another or update the labels or components in bulk for all issues.

Is there an alternative available?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,831 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot