Need advice to create a new JIRA business project

[Pankaj Sharma]

We have to build a small project in JIRA Cloud for our internal Business Task management.

PRIORITIES - For higher level management perspective, to have High level details of the business priority projects.

MILESTONE -Each priority would have many Milestones where a large PROJECT is broken                           down in to many Milestones.
                                 And each Milestone will have many sub-tasks.

So, it would be like below structure

PRIORITY 01
    Milestone 1 
          Subtask 001
          Subtask 002
    Milestone 2
          Subtask 001
          Subtask 002 

PRIORITY 02
    Milestone 1
            Subtask 0001
            Subtask 0002
            Subtask 0003
            Subtask 0004

It seems I should create new Issue Types :

PRIORITY and MILESTONE ( standard issue type)

> However, in this case, I am wondering how Milestones will get nested under its respective PRIORITY.

> And how we can view/create above structure Report in JIRA cloud.

Appreciate suggestions/advice. We are new to JIRA so your right approach/advice is much appreciated.

[Petter Gonçalves]

Hello Pankaj,

Welcome to Atlassian Community!

I've understood that you would like to use three hierarchical levels of issues in your JIRA instances: Priority -> Milestone -> Subtask.

In fact, JIRA works with three levels of Issue Types:

Epic -> Standard Issue types (Task, bug, Story) -> Subtask

You can easily create another standard issue type as "Milestone", however, Epic is the unique issue type available at the higher hierarchical level and although you are able to rename Epic to "Priority", I would not recommend it by the following reasons:

1 - The link between Epic and Standard issue type is made by a field called Epic Link that can not be renamed. That being said, it will be counter-intuitive for your users to know how they can link Priorities to "Milestones".

2 - JIRA has a field called "priority", used to inform the priority of issues. It can cause confusion for your users if both field and issue type have the same name

That being said, I would recommend you to use the structure:

Epic -> Milestone (New created Standard issue type) -> Subtasks

To link Epics to milestones, you just need to fill the Epic link field in the child issue or click to link a new child issue in the Epic issue, as explained in this documentation.

To create sub-task issues, you just need to navigate to the parent issue > Select more (•••) >  Create subtask. You will see the Create subtask screen, as explained in this documentation.

About the report you want to create, can you provide us with more details of what kind of report you are looking for?

We will be waiting for your answer to provide you further help you. :)