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 3 years ago
in Epic
2
Future consideration
Provide a means for bulk deleting saved views/reports
Every so often, it becomes necessary to do some house cleaning on saved views/reports as they can accumulate and become obsolete over time. Currently, the only way to delete a saved view is to go into the "Edit & Share" modal for each view and...
Matt Case
almost 8 years ago
in Reports
3
Future consideration
Allow 'does not contain' filtering on Tag type fields
I've got a very long list of features, and we tag them with clients who have requested them. I need to search for features that DO NOT have a certain tag, so that I can either A) make sure I've tagged them all, or B) find out what items aren't dri...
Kaitlyn Moore
almost 5 years ago
in Reports
0
Future consideration
Ideally we'd like to store properties about a user within the user object it self.For example we have members in our corporate directory who aren't actual employees, potentially we'd like to key of a property that indicates that to allow us to tai...
Nigel Lawrence
over 2 years ago
in Account settings
1
Future consideration
Alert when moving a feature from one product to another
We love Aha! for it's flexibility. However, it would be great to configure something platform wide (our platform). We would love to be able to have warnings if the user tries to move a feature from one product to another. This happens to us (accid...
Guest
over 9 years ago
in Features
1
Will not implement
Pain-point: multiple FINRA users complained about unintentional date changes while navigating Roadmap View. Idea: allow to control mouse-actions and in-place editing on the screen/view settings level.
Andriy Fomenko
almost 2 years ago
in Roadmaps
0
Future consideration
We need the ability to manage a backlog/ parking lot of initiatives, so that we can plan our product strategy without listing them definitively in the initiatives area.
Background as to why we cannot use ideas: We have an intake process that ca...
Guest
over 5 years ago
in Strategy
0
Future consideration
Maintain record links when promoting an idea to an existing feature
When promoting an idea to a new record, the dependency linkages get carried over from the Idea to the new record. However, when promoting to an existing record, this does not happen. We rely on this carry over so that PMs do not have to do extra m...
Ankar S
over 3 years ago
in
0
Future consideration
Please Add a Setting to Turn Off the Automatic Imports of Unlinked Jira User Stories
I believe that the way integration is currently implemented is based on a faulty assumption, e.g. that customers want all user stories created in an integrated Jira project and board to be sync'd to Aha!.
We'd much prefer that this not be the ca...
Doug Wilson
almost 5 years ago
in Jira
1
Future consideration
It would be beneficial to Product Line Managers and Product Managers if individual custom components could be hidden from some individuals. This is useful when adding sensitive financial data or other secure information. If the Product is shared f...
Guest
over 9 years ago
in Account settings
7
Unlikely to implement