Master epics should automatically inherit start and end dates from the release dates where the epics reside
With a master epic you can enter a start and end date, or have it be automatically calculated. The problem/idea is that this automatic calculation of start and end date should be based on the release dates for the releases in which the epics reside.
Guest
over 4 years ago
in Epics
2
Future consideration
Sometimes I use Features Board to discuss with internal stakeholders, and I don't feel comfortable showing internal release date there. External normally has some buffer and more generic (like a quarter of the year, when I am planning to release)....
Pablo Perez
about 9 years ago
in Features
6
Unlikely to implement
Reviewer role should not be able to change idea status
There is a good use case documented for Reviewers to be able to edit ideas they've submitted in an ideas portal (https://big.ideas.aha.io/ideas/APP-I-2648). However, allowing them to change the Status of that idea is not a good idea. This is and s...
Michael Tucker
over 5 years ago
in User management
2
Future consideration
Feature IDs should change when moved from one workspace to another.
What is the challenge? Feature IDs do not get updated when moved from one workspace to another What is the impact? it is confusing to know where it actually belongs Describe your idea when moving an idea to another workspace/release, update the ID
Mary Daul
about 1 year ago
in Features
0
Future consideration
Archive 'In-active' product workspaces last active after 90 Days
What is the challenge? As an Aha Administrator, how can I run a report to identify In-active Product Workspaces in Aha? Currently I run a dashboard report; 1) all workspaces and 2) each workspace records type ‘Max Values’, i.e. Goal, Initiative, I...
Mike Jacobson
about 1 year ago
in Account settings
0
Future consideration
Automation Rules are incredibly powerful but are limited to a very small subset of standard fields per item (ideas, epics, features, initiatives, etc.). We're constantly finding ourselves wish that a standard field would exist so that we can creat...
Conner Helton
over 2 years ago
in Automations
1
Future consideration
I use a pivot table to map several master features from different products on various stages and it works fine, but I would really love to see them as cards from board view. They provide much clearer look.
Pavel Egorkin
almost 7 years ago
in Reports
2
Future consideration
Prioritization Report - Allow more than one level of record structure
On the feature prioritization report, under the “edit columns” option, when I select “+ Add records related to this epic” it returns a blank list. I’d like to add initiatives to this list. This is needed when Epics are linked to Initiatives, but n...
Evan Hollohan
over 1 year ago
in Features
0
Future consideration
I have an existing library of content in OneNote. I'm exploring Aha! Develop to manage my product development, and would like to migrate my OneNote pages into Aha! Develop.
Jeff Tucker
almost 4 years ago
in Knowledge bases / Notes
0
Future consideration