ADD A NEW IDEA

All ideas

Showing 6218

Ability to archive custom fields

We have a large set of custom fields and the fields evolve over time. This means fields are withdrawn from use periodically, but there's no way to mark a custom field as archived and so prevent it from being available to include in a layout or rep...
Sophie Ramsden 9 months ago in Account settings 0 Future consideration

Allow multiple one-to-many custom tables on a single custom tab

I have information that I'd like to group under a single tab in my record layout. The information I'd like to capture requires the use of multiple one-to-many custom tables. Instead of housing this related information on separate tabs for each cus...
Bonnie Trei 10 months ago in Application 1 Future consideration

Lock poll during empathy session

During an empathy session I want to lock a poll so we can move onto another question, poll or topic with the results fixed. This similar functionality to Slido.
Daniel Lynch 10 months ago in Voting 0 Future consideration

Reports specific "notes" column

Like calculated columns, I want to be able to add a column to capture information or a note that is report-specific. The content of this column does not need to be included on the actual record layout of the item in the report. Ideally, this field...
Bonnie Trei 10 months ago in Reports 1 Future consideration

Add views to Aha! records

It's possible to Add Aha! view to notes. We need the ability to embed views into records. We are often referencing work (in lists and pivots) within our records but we have to manually type it out.
Nathaniel Collum 10 months ago in Features / Reports 1 Future consideration

Update the Release associated with an Epic or Feature using Automation

We've integrated Aha! Roadmaps and Jira but the release information is not being synced. We can use automation to copy the Epic/Feature Release name to a custom PI field and use the integration to sync the custom PI field with Jira. But when the P...
Sandy Kobayashi 10 months ago in Roadmaps 0 Future consideration

Scope / granular permissions for API Access

Hi All, currently every user with Aha! access can create an api token or authorize Apps to use the Api. And the Scope is tied to the user itself and not configurable. When it comes to projects, utilizing the API, it is the Application Owner / Admi...
Oliver Berger 10 months ago in API 0 Future consideration

Add Workspaces linked record options under related

We have our workspaces broken down by teams. Sometimes a team may need to make changes to an area of the program that is owned by another team. We need a way to document this. It would be great if under the related section - Linked Records, we had...
Brett Wilmeth 11 months ago in Releases 1 Future consideration

Missed required fields in Ideas should be more obvious

Folks are constantly thinking that they submitted ideas, but in actuality they missed a required field but didn't identify it before closing the window. Instead of the small red "This field is required," we'd recommend either not letting the user ...
Kristina Ursin 11 months ago in Ideas portal 1 Future consideration

Ability to set a default landing page per workspace

When using a centralized workspace for Ideas, it can be confusing for users to navigate to other pages like the Features board when going to the Ideas workspace from another workspace. In some cases users are taken to sections of the navigation th...
Stephanie Lechner 11 months ago in Account settings 0 Future consideration