Application
Sort by:
Trending
Status:
Showing 7713
1
VOTE
Allow extension settings implemented via react component
Extension settings are such a good place to automatically set up custom fields, extension fields, or perform any other necessary actions for extensions to work properly. Current settings specification is very limited and doesn't allow this kind of...
0
Future consideration
1
VOTE
Tailor help content to template language
Since choosing a different template in Aha for my workspace has changed all of the terminology, it is very confusing to try to follow along with the support content. The video content might be too much trouble but it would be amazing if I could ta...
0
Future consideration
1
VOTE
1
VOTE
Dependency between tasks based on leadtimes
I'm look for an option to make a lead-time/dependency between two tasks. Within our cycles (life plants in this case), we have different tasks that are dependent of each other. If we sow in one week, we will plant 3 weeks after for example. We can...
0
Future consideration
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
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
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
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
© 2025 Aha! Labs Inc.•All rights reserved