I need a way to compare versions of Features/Requirements in a Release
Before pushing a release to Jira, we do reviews of Features/Requirements with engineering. This may happen several times and we end up with multiple versions of the Release details. This makes it hard to compare the difference between the old and ...
Aldon C
over 9 years ago
in Releases
2
Already exists
Playing with gantt chart can cause a lot of problems, especially when moving releases/stages/features using mouse - it will be great to have a chance to block dates. In my opinion it should not be possible to change "scheduled" and "shipped" relea...
Guest
over 9 years ago
in Releases
1
Unlikely to implement
The Parking Lot needs beefing up. If you have a lot of granularity to your Parking Lots (created Parking Lot A, Parking Lot B, ... Parking Lot Z) it gets hard to us UX wise. The gray expandable box on the Board view resulting in lots of scrolling....
Guest
almost 9 years ago
in Releases
5
Unlikely to implement
It would be great to be able to modify the attributes of a release phase using bulk edit. Example may be when a key milestone (common to all releases) needs to change across multiple releases. This would not be a common release date though (which ...
Justin Woods
over 4 years ago
in Releases
2
Future consideration
Engineering managers & team leads sit "in between" Aha! Roadmaps and Aha! Develop. They more than just team owner permissions, but not full workspace contributor permissions. Key use cases Team leads can provide initial estimates on features b...
Currently the functionality exists to color the bars by assignee but those colors are designated by Aha and we cannot customize them. This would be helpful for organization and allow associations to be standard across reports to make decisions qui...
Dylan Kogut
about 4 years ago
in Releases
2
Future consideration
Master Release show % Complete Based on Child Releases
On the Master, Release show the % Complete based on the Children Releases % Complete. This should roll up based on Total % Complete divided by number of associated Releases
Stephen Morse
over 5 years ago
in Releases
4
Future consideration
As PM I should have direct visibility to changing a Release Date, so I understand why I can't make the Release Date dependent on Milestone dates. However, I would like to be alerted anytime a Milestone that my release is dependent on, is scheduled...
Displaying requirements within the Retrospective report
Who would benefit? Our dev management team What impact would it make? Would provide much better insights into why a release went off track. Currently the "Records Added" section lists Epics & Features added after dev started. In our case, it's...
Sam Banks
about 1 year ago
in Releases
0
Future consideration
The Release Portfolio is a good start on providing the ability to visually schedule resources, but it lacks some simple and extremely useful features:
Simple leveling. There should be a way to assign resources to each feature, and level the sched...
Kristian Kauper
almost 10 years ago
in Releases
2
Already exists