Our company has JIRA for many different project groups. I am running one group and wanted to use Jira Portfolio. The default hierarchy is that both the Stories and Tasks appear under the Epics. I sent a request to the JIRA admins to update the hierarchy configuration so that Tasks appear under the Stories per https://confluence.atlassian.com/jiraportfolioserver/configuring-initiatives-and-other-hierarchy-levels-802170489.html since that is how we organize our projects: Epics have Stories and Stories have Tasks/Sub-Task. We don't want Tasks under Epics. We want to be able to organize tasks under each story in Portfolio view and not have them be mixed up with the parent stories on the same level. I know I could hide tasks from view but that is not what we want, We still need to see the tasks, but under its parent story.
The Jira Admin stated we can't do this, as this change would affect all other Portfolio projects created in other JIRA projects (meaning, I'd have to track down owners of hundreds of Jira projects and see if this change would be acceptable). That is just not feasible. The documentation link above does state: "Note that any changes you make to the hierarchy levels in Portfolio for Jira will apply to all existing Portfolio plans." Or is this statement just badly worded and they really mean to say that a hierarchy change would apply to all existing plans created within the scope of a Jira project? If that is what is meant, it makes sense and is ok.
So, Is there a way to change the hierarchy for Portfolio within the scope of one Jira project. I can't be the first person out there to wanting to use a different hierarchy than other projects in a large organization, right?
Many thanks in advance!
