Application
Sort by:
Trending
Status:
Showing 7580
1
VOTE
Allow NON-Product Owners to generate Pull Requests over Release, Feature or Strategy fields
In a distributed team, not always the Product Owner (Product Manager) is in charge of all the aspects of a release or a feature. A typical example would be dates, where a Service Manager owns the date changes. In this situation, and when we do not...
0
Unlikely to implement
1
VOTE
larger formatting, character display for file names and captions
When I look at the "Files" screen, (or see files attached anywhere), they are surrounded by a lot of whitespace but the file names and captions are small, truncated, and hard to read, and there is no hover-over to show you the text you aren't seei...
0
Unlikely to implement
1
VOTE
1
VOTE
Better rank history of a requirement
When I move the order of a requirement within a feature and then I need to view the history of that change (with History button on the requirement), I can see the position change within what seems to be a technical rank ID (see attachment).
The n...
1
Unlikely to implement
1
VOTE
Add a "GUI/User Interface" category for ideas suggestions
There are a lot of ways to suggest improvements and enhancements to the GUI/UX. It would be good to have a category specific for those ideas when they are more about usability and clarity of design then the actual function being executed.
3
Already exists
1
VOTE
Add a "Views" category for Ideas
The "views" ('saved' and 'shared') are very useful, and there are a variety of ways to improve and enhance them. It would be good to have a separate 'ideas' category for 'views' instead of having to stick them all under "Features" (which is gettin...
3
Already exists
1
VOTE
Improve API returned data on list endpoints
Here at Namely we have a Data Warehouse and a BI tool where we monitor all of our services. Thus, we would like to get the Aha features and ideas on a daily basis. However, the list api endpoints for features and ideas are very limited, they only ...
3
Already exists
1
VOTE
Don't require Admin permission to create Products or Product Lines
As an Admin, I need to control who has a Paid Seat or not, to control costs. However, if a user has a Paid Seat, I don't care if they create Product Lines or Products, and I don't want to have to create the Product Lines and Products for them. For...
2
Already exists
1
VOTE
1
VOTE
