Feature board - Allow rows to visually display features and other work items in multiple sections on a single board view
On my trello-like features board, i have broken down releases (columns) into quarters (Q1, Q2, etc). so, i have one 'release' that is named "Q3 2017". Within that release, I have a list of 'features'. I'd like to group the 'features' into actual g...
Preston Rutherford
over 7 years ago
in Features
0
Unlikely to implement
BUG: master feature name doesn't display on the feature card unless a master feature exists for that product
In designing the feature cards for new products, the "Master feature name" doesn't display on the feature card unless a master feature already exists for that product, even though master features are turned on.
Guest
over 7 years ago
in Features
0
Already exists
Allow features to span across releases for better data model alignment between Aha and JIRA
Please allow features to span across releases for better data model alignment between Aha and JIRA.
Both Aha and JIRA have 3 levels in data model. Aha focusing on Why-What has Goals-Initiative-Features and JIRA focusing on What-How has Epic-Story-...
Guest
over 7 years ago
in Features
1
Will not implement
When I'm playing with my Gannt chart timelines, sometimes I accidentally move a bar when I don't intend to. Other times, I want to play with the dates to see how that affects my total timeline. Adding a "Save" button to the Gannt chart allows prod...
Guest
over 7 years ago
in Features
0
Unlikely to implement
If some one enters the wrong amount of time in the Work done input, it seems impossible to undo that.
Users should be able to correct mistakes, without having to delete and re-create the feature again
Guest
over 7 years ago
in Features
1
Already exists
Instead of using a seat (email / password), we would like to have an API key mechanism for authentication. This can be shared with the integration engineers and is not tied to an individual user.
Guest
over 7 years ago
in Features
2
Already exists
There is an approval process before a feature/release is record linked (set as a dependency) to another feature/release
This is useful for us since on how we use AHA, its our technical guys who does the linking of dependencies in terms of other features/releases to another. There are internal processes in terms of approval before a certain dependency (record link) ...