How correctly manage Jira project with multiple project phases

[Pier Nicolò Pinna]

Hi all,

I'm going to define a new structure of the Jira Project for my company. The requirements are:

• One project
• Different phases (Development, planning, release management ecc...)
  • Each phase, in turns, has different phases with different workflow, task, sub-task
• It has a status report for each phase
• It has status report of the project situation

I am thinking about hierarchy issue level like: story --> epic --> task --> sub-task but, unfortunatly, we actually have Jira v6.4.8 whitout add-on. 

I have no restriction about the structure of the project... I can work with workflow, issue type ecc...

Witch is the best way successfully satisfy this requirements?

Thank you all for the support

[Victor Florin Pana]

Just my cents on this: I think that the "One project" requirement makes the other requirements more or less impossible...

But why would the phases have different workflows? For example in the planning phase, you will have To Do --> In Progress --> Done tasks as you will have in the Development phase or in the release phase and so on. An alternative is to keep the workflow open with transitions from any to any status and then, create different boards for each phase and map only the relevant statuses on those boards as needed.

[Pier Nicolò Pinna]

Hi @Victor Florin Pana, thanks for your answer.

Our phases are so complicated, for example the planning phase have this workflow status: Prototype list, prototype detail, project estimate, features list, project details.

The pre-production phases have: Pitch in progress, pitch to be approved, rejected, done.

And ecc ecc... Is this an over complication in the process?

Which could be a best method?

Thanks