What is the best portfolio and project management structure to use in Jira Software Cloud?

[Leandro Azevedo]

I am looking for the simplest and easiest to navigate and maintain portfolio and project management structure, like Epic -> Story -> Task ->sub-task for example . Does Atlassian have any best practice documentation for that ?

[David Nickell]

Just me.  My opinion only

I am surprised nobody offered ideas on this yet.  I have worked for a dozen (or more) clients over the years and the most common approach I've seen is :

1. Initiative > EPIC > Story .    You can use subtasks too but I'm not a fan.
2. Bugs
3. Support Request

NOTE: You have to have a Premium License to support more that 2 levels.  Do it :-) .  That will also give you advanced planning

Do Not try to outsmart the EPIC>Story releationship.   (For example, don't put something betweem them).  Much of the system expects that and you will only create headaches for yourself.

Do Use Components.  Let me say that again.  Do Use Components.   Later when you want to know how much effort it takes to modify part of your system, you can pull all the changes related to a Component.

Applying a little "Agile" to this discussion....

• A Story Should be completed within a Sprint.  If you are consistently missing your dates, make smaller stories.

Assume your software product has 3 main "Systems: Database, Web, and Mobile"

• An Initiative may be to "Integrate AI technology ...."
• Epics could be something like  "IOS changes required for AI Integration", "Backend Changes for AI Integration", etc...
• Stories might be "create new API payload for AI detail", "modify UI with an AI Logo", etc...

Bugs are bugs :-).   Support Requests are driven by Customer Services.

[Leandro Azevedo]

Great aproach! Thank you very much, @David Nickell !