On occasions, I have had to change the status of a release back to open and then close it again. This resends the release to everyone subscribed. I would like to be able to disable sending a notifications for this type of maintenance.
Rob Bedeaux
almost 9 years ago
in Releases
1
Unlikely to implement
Once development on a release is underway, things happen. Change Control should encompass approvals and permissions to edit dates and schedule, and rollback. Here are some requirements:
1. A product owner (or an "uber product owner", e.g. the VP ...
Guest
about 9 years ago
in Releases
1
Unlikely to implement
Ability to Define and Visualize Capacity of Release Phases
We are an agile software company that releases on a cycle of 3 sprints, each 2 weeks long. We can set our release capacity based on the # of development hours to determine about how many features we can commit to, but we also need to plan how many...
Guest
about 9 years ago
in Releases
3
Unlikely to implement
Add Parking Lot Releases and Features to Feature Roadmap and Release Gantt
Who would benefit? What impact would it make? I want to track upstream (pre dev) work in product and UX's lane to track true status end to end for our work. How should it work? When going into the features roadmap view I am trying to see my parkin...
Karla Johnson
7 months ago
in Releases
0
Future consideration
Add option to expand Gantt view when sharing as webpage
When sharing the Gantt view as a webpage, the option to expand items (such as releases and epics) is unavailable to viewers. By allowing this functionality, the viewer could get a high level of understanding and expand items of interest to gain a ...
Guest
8 months ago
in Releases
1
Future consideration
Add Workspaces linked record options under related
We have our workspaces broken down by teams. Sometimes a team may need to make changes to an area of the program that is owned by another team. We need a way to document this. It would be great if under the related section - Linked Records, we had...
Brett Wilmeth
10 months ago
in Releases
1
Future consideration
When copying a release, we need the ability to opt-in (or out) of copying features as well.
We plan major releases on a quarterly basis. Once we finish overall quarterly planning under the quarterly release in Aha!, we copy the make a copy of the major release to create 2 minor releases as well to ultimately create a monthly release sche...
Claire A
about 1 year ago
in Releases
0
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...