My votes
Sort by:
Trending
Filter by:
Status
Showing 9110 of 9110
3
VOTE
1
VOTE
Add the ability to approve log time entries in Aha! Develop for payroll purpose
In Aha! Develop, having the possibility to log time entries approval would be great. Doing so, it could have a whole dimension of cost tracking as well and budgeting. Combined with time planning capacity per employee would top it all.
1
Future consideration
1
VOTE
Adding people to paid seats in aha! develop is not as clear as it should be
I click into billing and see the open seats I paid for on Aha! Develop I click 'manage' assuming that would allow me to add seats to that arena of Aha! I get routed to Aha! Roadmaps with no clear way to get to the Users page of my Aha! Develop acc...
0
Future consideration
1
VOTE
If I don't have access to a release, I should not be able to assign an Epic to it
Our company has many different workspaces and releases. And it is very easy to accidentally assign an Epic to a release that I don't have access to, just by clicking within the Release area, and without my knowing it, the Release has suddenly chan...
0
Future consideration
1
VOTE
When editing a layout, search existing custom fields by 'internal name'
The internal name of a custom field is used to group together the fields that are applicable to a certain group or use case within the organisation. Creating standards for layouts requires custom fields for that internal name to be applied. Wideni...
0
Future consideration
2
VOTE
Add API support for retrieving integration details (target JIRA project + server url for example)
Allow automation of integration setup from other tools. In my use case, the intent is to be able to validate/cross-check what is actually configured on the JIRA side (admin only) with what is expected/desired on the Aha side (various project team ...
0
Future consideration
2
VOTE
Configuring workflow board should be reflected for all users
Currently, if I was to configure the feature workflow board (and/or feature cards on workflow board), the changes I made would only be reflected back to me. Every user of the workflow board has to then configure the board (and/or feature cards) th...
2
Already exists
3
VOTE
3
VOTE
As the "Owner" of a release, I would like to be able to close it so no new features can be added.
As releases are usually bounded by e.g. development capacity, or certain themes (marketing message) it should be possible to close a release if capacity is reached.
Closing means that the "owner" of the release can indicate that no more features c...
0
Unlikely to implement
2
VOTE
© 2025 Aha! Labs Inc.•All rights reserved