This question is in reference to Atlassian Documentation: Video tutorials
The video says "it is possible to create unlimited levels of hierarchy..." e.g. initiatives.
Our team wants to be able to define the following structure. Can you tell me how to maximize the use of Portfolio to support this?
Initiative is made up of Requirements. Requirements are made up of 0 or more sub-requirements, of infinite levels. Sub-requirements are implemented by stories, tasks, sub-tasks. So as an example
Req 1.1. -> Story -> Subtasks
Req 1.2.1 -> Story -> Subtasks
Requirements could go down infinite, but we could limit to say 10 levels.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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!
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