As far as I can tell, there is no way currently to nest a simple task or story into the initiative or hierarchy above epic for it to be included in the scope. There are a few bodies of work that are too small to be an epic, but are part of an initiative.
As seen below, Portfolio only gives the option of added epic when adding new issue under initiative. My current Issue Type hierarchy is: Initiative > Epic > Story/Task
If this is true, Portfolio forces the user to have direct nesting as seen here https://www.atlassian.com/agile/project-management/epics-stories-themes :
This forces me to either
All of these are not incredibly helpful. Is there a workaround, something less clunky, or potentially something that I am doing wrong?
Thank you for reaching out.
I'm not sure of what kind of functionalities and dependencies you want to create between the initiative and the Story/task, but an option to achieve that "Connection" between both Issues would be to use the default Jira issue link:
You could simply create a link type with the name that would better describe their relation and properly link both issues. Would that be an option for you?
Let us know if you have any questions.
Hi everybody 👋 My name is Roi, Portfolio for Jira product manager. Today I'd like to share with you the release of an early access feature to help you visually represent team commitments at ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events