Account settings

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...

If I search Big Ideas, I can find multiple ideas relating to 2FA - including requests for Yubikey support and Google Authenticator without SSO. I want to dial it back a notch... today, in 2021, I am unable to turn on 2FA to protect our Aha! creden...

I have several workspaces under a product line, and when I drag one to change the order, the view refreshes and the product line collapses. It's annoying to have to re-open the parent line each time, and makes the operation take a lot longer than ...

For predefined choice list fields When displayed on portal, show tool tip text in the empty field space, similar to the predefined tags field. We know a tool tip exists with hover over, but would be more obvious to submitter if seen in the field l...

it would be useful to be able to designate the type of field that results from a calculation to determine how this field behaves. In our case, we are using calculations with text to compose a URL that we want to be clickable. The URL custom field ...

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 ...

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...

Topic: Custom Fields cut off and do not show the entire name Issue: When I select a custom field and I hover over the '...' it does not show me the rest of the custom field name. (See screenshot below) Use Case: When we select custom fields, we wa...

Aha! does not allow importing of custom fields at product level. This will be useful if that can be supported.

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...