All ideas
Sort by:
Trending
Status:
Unlikely to implement
Showing 1526
5
VOTE
Allow Requirements on Master Features
We use master features to define use cases that require work from multiple products. The features linked to the master feature come from those different products. However, we need the ability to put requirements on a master feature to be able to t...
0
Unlikely to implement
5
VOTE
Add Mock ups as an available column when reporting on Features
We are trying to enforce change management needs by requiring production changes have a screen shot of the new / edited feature. We are doing this at the Feature artifact by asking our users to ensure the Feature has this prior to updating the Fea...
0
Unlikely to implement
6
VOTE
Ability to 'hide' columns when printing / publishing
When viewing our list of ideas or features, we have to add columns to sort the list the way we want. However, these make the list look messy when we're presenting to others. It would be good to use these columns to sort the list the way we want, b...
0
Unlikely to implement
4
VOTE
Use Confluence RBAC to control access to embedded reports
I want to publish a report to group of Confluence users but I don't want them to be able to re-share the original public link, that it's not just easy to lift but you have a button to show it!
In other words, have a way to publish the Shareable ...
0
Unlikely to implement
4
VOTE
Filter search to a product
When I want to link a feature to another feature, or a feature to an existing epic, I sometimes do not know the exact name or ID. I will search some keywords, but because the Aha workspace I live in is so huge, I often will have many results for t...
0
Unlikely to implement
6
VOTE
Configurable relationships in the Dependency Map
I'm glad to see the dependency map feature appear. However, I notice it doesn't just show dependencies, it also shows "relates to" relationships. On the map, they are indistinguishable, which is confusing. It would be great if I could limit the ty...
0
Unlikely to implement
6
VOTE
1
VOTE
Record level permission restrictions
What is the challenge? Some features or initiatives are sensitive, so we would like to be able to set record level permission restrictions What is the impact? Anyone who might come across work that isn't being widely publicised in the org Describe...
0
Unlikely to implement
3
VOTE
6
VOTE
It would aid management of features if expand Assignee field to enable population with more than one individual Assignee
In our development projects, features are often owned/assigned to more than one individual. Per intended use of the To Do's, we prefer to assignee the true list of owners to each feature versus creation of a To Do or use of the Program Manager fie...
0
Unlikely to implement
© 2025 Aha! Labs Inc.•All rights reserved