All ideas
Sort by:
Trending
Status:
Showing 8935
6
VOTE
Make Initiative views in Notebook more useful by adding descriptions and comments
Right now, neither the initiative list, nor including initiative detail is very useful in a notebook.
The list of initiatives doesn't have enough information to be useful -- it would need the description, at minimum to be useful to me, and it tak...
4
Will not implement
1
VOTE
Enable Google Keep Move and Pin
It would be great to allow for cards (epics, features, requirements) to move in any "card" based view. A great example is Google Keep (Web version on Desktop). Google Keep allows for easy moving of cards and pinning of favorites to the top. Add in...
0
Future consideration
1
VOTE
better validation warnings and units tips and handling on estimates fields
the toolips on estimates fields need consistent messaging in all field contexts, with proper messaging/tip content based on the units of the configuration. this needs to be the UX when creating (actual configured units not a hard-coded either/or t...
0
Future consideration
1
VOTE
please let admin better control the field choices on apply rank to users cannot make bad choice
apply rank opens a picker to let user decide which custom field to apply the rank value to , and that custom field needs to be the field in the mappings that provide update into target tooling (my case, its ADO, stack rank). I see multiple custom ...
0
Future consideration
1
VOTE
Allow using automation to change the parking lot of new features in Aha Develop
When creating automation for features in Aha Develop, it's not possible to change the parking lot (workspace) of the feature. There is a variety of fields that can be changed, but unfortunately, the parking lots are not among them. This would help...
0
Future consideration
2
VOTE
Public API for Ideas Portals
Provide a public API (as part of the Aha! REST API) which can be authenticated against using an Ideas Portal SSO token (JWT) the same way as we do authentication for the web version of Ideas Portal. This means the API's logged in user would be an ...
0
Future consideration
5
VOTE
Leave product hierarchy expanded after saving changes to a product.
I have a multiple tiered hierarchy set up for my product lines with sub product lines. When I make changes to multiple products, I use the configure product/product line tool to give me a visual representation of the product hierarchy. If you dril...
1
Already exists
3
VOTE
Release Template Start date should be the start date of the release
It would be ideal when you add in the release phase template to the release the dates start from the development start date. This would then prevent having to reshuffle the milestones as the dates are not aligned to the release.
0
Future consideration
6
VOTE
When I move a feature to the parking lot in Aha, it should move to the icebox if it exists in Pivotal
Most sprints priorities will change a little bit as time goes on and it will be appropriate to remove a ticket that was added previously. Likewise, if a sprint is over subscribed some tickets may roll over into the next sprint.
When this happens, ...
0
Will not implement
1
VOTE
Better presentation of text when integrating to an existing field in ADO
Sometimes, the feature in ADO already exists, and I want to link it to a feature in Aha. When I do this, I'm presented with an un-readable HTML output of the description fields, making is pretty much impossible to actually see the differences. See...
0
Future consideration