Adding a New Hierarchy called "Theme"

[DEAA Tools [Steve Masturzo]]

Hello,

we have been actively using Portfolio for over 2 years. Currently we have hierarchy as Initivative -> Feature -> Epic. Some of teams want to add "Theme" as a new Issuetype and at the top level of hierarchy. Will this impact any functionality of the other users who do not want to see this change. I know hierarchy for portfolio is global and cannot be set on project level. Please advice.

Thanks

[Stephen Wright _Elabor8_]

Hi @DEAA Tools [Steve Masturzo]

It shouldn't be an issue if added to the top of the hierarchy.

It's true that all plans will now have Theme in them - although users can choose to view from Initiative downwards, meaning for those who don't want Theme this should have minimal impact.

From an issue perspective - it would mean users could relate their Initiatives to any created Theme via the Parent Link. You could check compliance here through issue searches.

If you want to discourage creation of them in projects who do not see a need for them, you could just add Theme to projects' Issue Type Schemes who want them, meaning certain projects would not have the option to create them?

Ste

[Thomas Towkach]

If the other teams don't use Themes I don't see a problem(eg, they may have the option available, just don't use it. The hierarchy down should work as before,

[Ravi Sagar _Sparxsys_]

The hierarchies are global and the issue types will be mapped to it will be reflected in all the plans using it.

Ravi