Project Hierarchy

[Rita Deo]

We use Jira Software cloud within our team.  I need some help in creating project structure 

Main Application

Module 1 /Project 1

Story1 :

     TAsk

        SubTask

Module 2/Project 2

 <Same as above>

There are front end,back end, api components associated to these tasks. Should i create Main Application  as epic? or Project?

Should I use Module 1/Module 2 as components and then use labels UI,Database ?

Thanks,

Rita

[Dave Rosenlund _Trundl_]

Hi, @Rita Deo. Welcome to the community 👋

The first thing to consider is that Jira out of the box expects an Epic > Story (or Task, or Bug) > Subtask hierarchy.   It does not expect a Tasks to be the child of a Story.  Advanced Roadmaps, which comes with Jira Cloud Premium will let you define a new parent above the Epic, and something above that parent, too, but it also expects the same 3 level hierarchy below starting at the Epic level.

That said, many organizations do craft their own hierarchies  -- or even different hierarchies for different projects using an Atlassian Marketplace app to manage them.

I am showing just the first row of results. There are many that you may want to consider.

That out of the way, IMO there is no right or wrong answer to your questions.  You can arrange your work in whatever way you'd like.  However, what see most frequently in this case is each product is in it's own project.

If you choose to use a product that let's you create and manage hierarchies as you see fit, most of those will also let you create a board that looks across those projects (products).  At least I know for sure the first one, Structure, does. 

Full disclosure, I work for the company that makes Structure.

Hope this helps,

-dave