Account settings
Sort by:
Trending
Filter by:
Status
Showing 471 of 8115
1
VOTE
Allow "Advanced Estimates" for Ideas
Based on this Aha Page, Advanced Estimates can only be added to Initiatives, Epics, and Features/Activities. In our environment, we need to identify team impact early on at the Idea level. These not work requests, but rather an identification of w...
0
Future consideration
1
VOTE
Allow re-association of custom table records with other objects
Currently custom tables and their records are permanently associated with an object (i.e., workspace, Epic, Feature, Ideas, etc.) and don't get copied when the parent object is copied and cannot be moved out of an object. It would be best if you c...
0
Future consideration
3
VOTE
Clarify the use of the term "allocate seat", as it's not clear a seat can be unpaid. :-)
Hi, I had a human-error issue where I had two users in my user list that I couldn't figure out how to give them view access. I clicked the viewer access button, but nothing would happen. It turns out it was because I wasn't clicking "allocate seat...
0
Future consideration
4
VOTE
Batch changing of users from Password to SAML/SSO
We recently instituted SSO on our Aha account, but currenlty have a couple of dozens folks who have the typical username/PW login profile active. I'd like to make a universal/batch change to force all users to log in via SSO, however there is no c...
4
Future consideration
2
VOTE
Set default navigation per Aha! role
As an Aha! admin I want the ability to set a default navigation for specific role types. For example, most of my users that are Viewers do not need to have access to the Strategy section. There are some exceptions though, so ideally I would be abl...
0
Future consideration
4
VOTE
In workflows, add the ability to limit setting a certain status to certain users.
In workflows, most of the time a status like "approved" is available. However, at the moment everybody can set this status, so it pretty useless.
If only certain users (e.g. with a certain role) could set the status to approved it suddenly gets ...
2
Unlikely to implement
1
VOTE
Make "Statuses" in workflows their own object that can be adopted within status workflows
Currently, the way the Status Workflows are setup, each workflow is completely independent from other workflows, even when most of the same statuses are reused across these workflows (teams just want to add one more status). The result of this, is...
0
Future consideration
1
VOTE
Add a filter to Account Settings - Custom Fields by Used in Layout
User, needs to filter by 'Used in Layout' in the Account Settings for Custom Fields, to easily view fields used in specific layouts and more easily edit specific fields per layout, or to see or not see fields that are not in a layout. This would i...
0
Future consideration
1
VOTE
Make New user message easier to edit and away from security
We have a custom New USer message but when you go to edit it the entire message disappears so if you just want to remove a name you have to reenter the entire message. It is also closely tied to the security area and should be separate so that the...
0
Future consideration
3
VOTE
Alternate hierarchy to manage work through different lens
We look at the same Initiatives through two lenses: (1) the product lens, which Aha! solves really well; and (2) the program lens, which Aha! does not solve for.
The idea is to have an Alternate Hierarchy in Aha!, such that the same initiative c...
0
Unlikely to implement