The video says "it is possible to create unlimited levels of hierarchy..." e.g. initiatives.

[Rick Barlow]

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

Initiative A

    Req 1

        Req 1.1. -> Story -> Subtasks

        Req 1.2

               Req 1.2.1 -> Story -> Subtasks

etc.

Requirements could go down infinite, but we could limit to say 10 levels. 

[María]

Hello Rick,
You can learn how to create your hierarchy here. I hope you find the docs useful.

Cheers, 

[Basse Hauke_ BKW Energie AG]

The described solution is very complicated, and not a practically usable support of hierarchy, I'd say. It is okay for adding, as it proposes, one or two levels above epics, but not for creating an outline-like requirement structure.

Just look at how it is done in old "Quality Center" / "ALM" software: You can have as many levels as you want, without admin configurations. Every requirement ony any level can have any "issue type". 
There is a visual tree that you can use, or that you can ignore.
You can export it to word, and the structure is turned into Word chapter structure.

For me, this is the biggest reason not to use Jira for requirements. (For support tickets it is great; for requirements in large projects it isn't.)

[Vasiliy Zverev]

You also could try using Structure plugin: https://marketplace.atlassian.com/plugins/com.almworks.jira.structure/server/overview

[Rob Woodgate]

Hi Rick,

I've added the jira-portfolio and portfolio tags to make sure the portfolio users see your question.