ADD A NEW IDEA

My votes: Account settings

Showing 77

Add Product ID as a field to the Workspace Info Tab

The only way users can see the workspace Product ID is to pull a report. As a result, our workaround is to download the Product ID and upload it to a custom field on the workspace layout. This is a lot of manual work for something that is inherent...
Cindy Datlof almost 4 years ago in Account settings 4 Unlikely to implement

Custom logo on the login screen

From a branding standpoint, it will be great if we can customize the logo on the login screen, instead of the default "Aha!" logo. THanks
Guest over 9 years ago in Account settings 0 Unlikely to implement

Restrict Viewers to specific Aha section views

Currently we use web reports linked from Confluence to restrict the visibility of registered viewers on certain product roadmaps. However, the report view isn't really as good as the default Aha view which is much easier to navigate. But giving Vi...
Guest almost 7 years ago in Account settings 0 Unlikely to implement

Adding 'Net New' users should be restricted to Admins only

Issue: Product Owners are able to add Net New users to a companies Aha instance This is sorta a big a deal as a Product Owner may not understand the nuances involved in adding a new person into Aha from an administrative point of view. (I understa...
Joe Carpenter over 8 years ago in Account settings 1 Unlikely to implement

Enhance Text Editor With Code View

Would be great to have an option to enable a Code View for anywhere the text editor appears throughout the app. I understand not everyone would want this, but if it could be an option where the user could elect to have a Live View tab and a Code t...
Guest over 7 years ago in Account settings 0 Unlikely to implement

Disabling anything to do with Time logged for 'reviewer/viewer' access levels

We have a requirement where we are using Aha for our time entry and ultimately invoicing. However currently if we share it with our clients, they can see any/all time entered immediately before PM's have had a chance to review time and determine i...
Guest about 8 years ago in Account settings 0 Unlikely to implement

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

Batch changing of users from Password to SAML/SSO

We recently instituted SSO on our Aha account, but currenlty have a couple of dozens folks who have the typical username/PW login profile active. I'd like to make a universal/batch change to force all users to log in via SSO, however there is no c...
Joe Carpenter almost 9 years ago in Account settings 4 Unlikely to implement

Extend product tree to support different configurations of a product line

I manage a product line where each product has different configurations. Currently I get around it by making different releases, but it really doesn't solve the problem because the different configurations have different requirements. So, being ab...
David Spada about 9 years ago in Account settings 1 Unlikely to implement

In workflows, add the ability to limit setting a certain status to certain users.

In workflows, most of the time a status like "approved" is available. However, at the moment everybody can set this status, so it pretty useless. If only certain users (e.g. with a certain role) could set the status to approved it suddenly gets v...
Guest about 9 years ago in Account settings 2 Unlikely to implement