ADD A NEW IDEA

Application

Showing 7505

Hide workflow approval groups on to-do when no workspace users assigned

What is the challenge? All account approval groups populate for the approval group field on approval to-dos, even when no users from a given workspace are assigned to a group. This creates a challenge for someone to select the correct approval gro...
Jeanette Resnikoff 5 months ago in To-dos 1 Future consideration

Import from miro into Aha! Notebooks

I can see us dropping miro for the Whiteboarding in Aha! The problem -- we have a ton of whiteboards in Miro that we would want to keep working with, and copy/paste doesn't quite work (I copied and pasted from a mind map into a mind map in Aha! an...
Guest almost 2 years ago in Whiteboards 0 Future consideration

When copying a release, we need the ability to opt-in (or out) of copying features as well.

We plan major releases on a quarterly basis. Once we finish overall quarterly planning under the quarterly release in Aha!, we copy the make a copy of the major release to create 2 minor releases as well to ultimately create a monthly release sche...
Claire A over 1 year ago in Releases 0 Future consideration

Allow setting approvals to "any" or "all" when configuring automation rules to trigger approvals

Who would benefit? Users who require all members of an approval group to grant an approval What impact would it make? Right now it only allows "any" member which allows approvals in this scenario to proceed prematurely How should it work? Much lik...
Stephanie Lechner 7 months ago in To-dos 1 Future consideration

Allow to define the scope of tags/choice list custom field values (account vs. workspace)

It should be possible to define whether the values of choice list and tags custom fields (predefined or editable) are shared at account level (current behavior) or limited to workspace level such that workspaces can share a configuration but have ...
Thierry Loones over 1 year ago in Account settings 0 Future consideration

Option to restrict Features to the same release as the epic

Would like to see an option in the account / workspace to only allow features to be associated with the same release as the epic.
Guest almost 3 years ago in Features 1 Future consideration

Webhook Notifications from the User making the Change

Product Integrations are set-up by a system admin to run through a webhook. We used an Automated User account to set up the webhooks so it's not attributed to anyone specific but the feedback we get from users is that of frustration. PMs want to s...
Guest almost 6 years ago in Comments / Notifications 8 Future consideration

Ability to lock rows on reports/roadmaps

We have a dashboard that shows our roadmap and some other KPI reports -- our roadmap is long, so individuals need to scroll to see all roadmap rows in this dashboard view. Would be nice if we could lock the row which shows the roadmap dates for th...
Danielle A almost 3 years ago in Roadmaps 2 Future consideration

A method to effectively control and manage API access in Aha!

Who would benefit? Aha! administrators What impact would it make? It would help track the API usage across the instance. For example, if someone is generating heavy traffic by creating thousands of Aha features per minute, we as admins need a meth...
Alok Dath 7 months ago in API 0 Future consideration

Automatically link feature to epic from work requests

When a feature is created from a work request of an idea/epic, the features should be automatically linked to the epic (it is created as a related record, but we need the manually link the feature). The link should be be automatically created so d...
Connie Lin over 2 years ago in To-dos 0 Future consideration