Missed Team ’24? Catch up on announcements here.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Best Practice in Portfolio with Releases/Versions

Kristi Curry
Kristi Curry
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
November 19, 2018

I am looking for a way to roll up work into higher level deliverables and milestones.  The team uses the "JIRA Version" for continuous deployments and integration so I am having a conflict with the concept of Releases in Portfolio.  Wondering if maybe setting up release streams is the way to go and then the team can add whatever version to that release stream?  Challenge here will be when work across projects is bundled into a version.  Anyone gone down this road and have any advice on setting up a hierarchy that goes from a Product Feature/Theme>Initiative>Epic>Story>Sub-Task?  This is a massive project (2-3 years and will have over 30 Product Feature/Themes that drill down.  I want to be able to show progress against the entire program.

Answer
Watch
Like brad.mcbrayer likes this
254 views

1 answer

0 votes
brad.mcbrayer
brad.mcbrayer
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
November 26, 2018

We have same problem.  Kristi.  We just started looking into solutions.  

Reply

Suggest an answer

Log in or Sign up to answer
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

    See all events