ADD A NEW IDEA

Account settings

Showing 621

Ability to assign multiple custom roles

It is currently only possible to assign a single custom role to a user. As an admin, I often define multiple distinct custom roles with very specific permissions. For example, a custom role to administer capacity planning and another custom role t...
Mark Eaves about 4 years ago in Account settings 0 Future consideration

Allow non-admin product owners to configure tags

Our teams are using tags heavily to add planning metadata to features. Over time, duplicate and mistyped tags are introduced which can cause confusion. At the moment, only those with admin access (one person within our organization) can clean up a...
Gordon Cloke about 6 years ago in Account settings 0 Future consideration

Allow deletion of types and other data while still in use

There are several places in Aha! where we disallow a user action because an object is in use. For example, users can't delete a custom type while records are using it. We already have an elegant solution in place for this when changing from one wo...
Bryan McElhinney about 2 years ago in Account settings 0 Future consideration

Assign Custom fields to a parent workspace

We have over 250+ custom fields being utilized by various workspaces. Because we cannot assign a custom field to a particular workspace all 250+ fields are visible in every filter in every workspace. If we could have the ability to define which wo...
Jake Ludwinski about 4 years ago in Account settings 4 Future consideration

Attach a link

In addition to being able to attach files, it would be helpful to be able to attach links. Many times, relevant information is a web page instead of a file. Today, we can only embed links in text fields, such as Description and Comments. I put thi...
Tom Beck about 6 years ago in Account settings 3 Already exists

Ability to create custom fields with context

When we create custom field in AHA we want the ability to create context for each product so that we can see only values which are relevant to a specific product. For example Team A, Team B and Team C are related to Product 1, we do not want to se...
Guest about 6 years ago in Account settings 0 Already exists

Inconsistent / Broken Terminology

Within Marketing, Business and Project Lines, the customize terminology setting is broken and creates an inconsistent user experience that confuses users. Within the 'Customize Terminology' setting (Settings > Product Line > Terminology), if...
Carl Ambrus about 4 years ago in Account settings 0 Future consideration

Line and Workspace management - stop collapsing the Line / Workspace hierarchy each time you complete a Line

If we leverage UX / UI, when a user-persona leaves a data structure in a window, they should expect it to remain the way they left it when they return, or complete a task Currently, when I go to the Customized Workspaces --> then expand some or...
Guest about 4 years ago in Account settings 0 Future consideration

permission-restricted release or feature status

We should be able to configure specific release statuses so that they're restricted, editable only by certain users or user groups. We have a Program Management group which maintains an authoritative list of releases the product organization has c...
Guest over 8 years ago in Account settings 1 Unlikely to implement

Opening 2-factor authentication to other providers

aha!'s 2-factor authentication implies signing up with a designated 3rd party. We would like to include aha! with the other solutions in our IT portfolio, for which 2-factor authentication is supported by a different supplier than aha!'s partner.
Guest about 4 years ago in Account settings 1 Future consideration