You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi, I work with a team and we are using Jira Portfolio. We are using releases to organize our work in portfolio as it is the concept that maps most closely to our business. We have many projects and many releases in the works at any given time.
- We would like to prioritize releases so that Jira schedules those issues ahead of lower-priority issues.
- We need to be able to prioritize releases across projects without using cross-project releases.
To get the algorithm to Prioritize with the release as the primary factor you should be able to set the Releases start date as "Relative to previous release date" and the release date to "Dynamic release date", the main concern is to make sure the release date does not overlap with the start date of the next release.
Automatic release assignment only works if there is at least one release defined with a fixed end date, so if you have the releases dynamic you would want to manually assign the issues into releases.
Earl, thank you, but that assumes that I have one track of releases, which I don't. I have several tracks of releases corresponding to different projects. I want to prioritize across projects by having one release for one project be more important than another release from another project, so the relative to previous release date is a non-factor here. How do I do this? Thanks.
Thanks for the additional details, Sprint assignment, Dependencies, Release assignment and Issue rank are the most important factor in issue prioritization, but this is at the issue level and can cross prioritization's between releases.
Within portfolio the prioritization efforts could be mix and matched with "Relative to previous release" "As Early as possible" or A "Fixed Date" to rearrange the releases for your desired layout, with a manual release association of issues to build out the plan. Primarily though if you Set a fixed release date on issues and then assign issue to the release this would prioritize issue based off the fixed date prioritization of the release as a leading factor for the time table
To expand on this however I would suggest checking out the app "Cycle Control" which has a feature for automating release prioritization in portfolio, However this one is only available in Jira Server, and if you're on Jira Cloud I believe that "Insight - Asset Management" also has a similar capability as well but I cannot verify if that is the case, as an alternate app choice to look into.