Account settings
Sort by:
Trending
Status:
Showing 513
1
VOTE
Interactive AHA data model should not show objects NOT in use
AHA offers the ability to disable Epics. However, with Epics disabled across all workspaces, the interactive aha data model ("How AHA works") still shows this data object and a relationship of Feature to Epic and a link of "Work with Epics". This ...
0
Future consideration
3
VOTE
Increase available text area in system broadcast when an image is not specified.
The new broadcast message format looks good when an image is specified, however when an image is not used it would be great if the message text could expand to make better use of the available space.
1
Future consideration
2
VOTE
Allow product owners to grant users with paid seats access to their products
As a product owner (who is not a paid seat group owner), I would like the ability to grant users who already have a paid seat (but not access to my product) access to my products so I can control who has access to my products.
0
Future consideration
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
3
VOTE
Allow the navigation order to be changed
I have restricted the navigation options depending on product line or child products, however I would like to resort the order that the navigation options appear - why does "Ideas" come between "Releases" and "Features". Logically "Ideas" should b...
1
Unlikely to implement
2
VOTE
Turn everything on by default
I ditched you during a trial because I couldn't find the features you promised on your website. Where is time estimation? Where is the Kanban board? If these are important enough to get modules on the site, they are important to users, and you kno...
0
Future consideration
3
VOTE
Allow for integration via OAuth 2.0 Service Accounts
Ask: Support OAuth 2.0 Service Accounts for auth on the Aha! API
Background: We use SSO (Okta) for user authentication (Aha! doesn't know about passwords by design). We also have a set of scheduled tasks (scripts) that query the Aha! API, summari...
1
Already exists
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
2
VOTE
Maintain item ID when Promoting/demoting
When changing a feature to master feature, to initiative and back (demoting), the item is recreated, resulting in a new id, and a new link. If a team is documenting the features/master features etc with links, this documentation will lose value wh...
0
Future consideration
2
VOTE
Allows us to use Display Name with OKTA
OKTA has a username & display name option, however, Aha! doesn't pull in the Display name to give you the option to visualize that or give you the option to edit the name. This is a frequent request from my users who do not go by a legal name....
1
Future consideration