Releases

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...

What is the challenge? We have multiple products and multiple releases happening over time. Each time a product owner creates a release note the formatting usually is different. What is the impact? The product owner then has to manually update the...

What is the challenge? Releases commonly contain more than 30 features What is the impact? Release notes generated with AI need to be run multiple times to cover all relevant records Describe your idea Remove the limitation of 30 fea...

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....

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...

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...

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...

Just a suggestion but in the 'Release Portfolio' view it would be great to have a collapse all/view all button that would open all sub phases (and features) to a releases rather than selecting to open/collapse all individually especially when feat...

Dates of release phases and milestones are auto populated whenever release phase templates are applied to releases. This is not a expected behavior, as most of the time dates are not confirmed yet when a release is created. This is confusing given...

Some projects can only be completed once another task is completed, so to have a gantt chart that only allows for finish to start dependencies restricts the ability to add proper linkages and forecast