ADD A NEW IDEA

Account settings

Showing 638

Ability to alphabetize a list of options in a field

Who would benefit? Admins What impact would it make? Save lots of time How should it work? A button or dropdown offering ways to sort the list options (ie: alphabetically)
Tommy Oakes 9 months ago in Account settings 0 Future consideration

Limit Name field in all objects to 255 characters

When integrating to Rally, integrations fail due to Rally's 255 character limit in the matching field. There are no error messages or notifications. This was determined through some back end research. In order to prevent this in the future, we wan...
Karla Johnson almost 3 years ago in Account settings 1 Future consideration

Ability to disable attachments in email

As a security manager and Aha! administrator, I'd like to be able to disable attachments from being sent in emails to ensure that security policy is followed and that all content shared in/via Aha! requires a login.
Scott Goldblatt over 7 years ago in Account settings 0 Will not implement

Require fields before record can be completed

We can require fields upon a records creation with the create record layout. But to complete a record, users just need to change the status to a status in the Shipped category. However, completing a record sometimes requires other fields to be upd...
Erik Johnson almost 4 years ago in Account settings 0 Future consideration

Allow moving of custom table records to other objects

Currently custom tables and their records are permanently associated with an object (i.e., workspace, Epic, Feature, Ideas, etc.) and don't get copied when the parent object is copied and cannot be moved out of an object. It would be best if you c...
Karla Johnson about 3 years ago in Account settings 0 Future consideration

Allow the selection of epic timelines as default view for Roadmaps > Features

Who would benefit? What impact would it make? How should it work? Allow the additional selection of epic timelines if epics are enabled for the workspace.
Chris Zempel 9 months ago in Account settings 0 Future consideration

Terminology customizations should persist throughout all screens when cascaded from Account level

We have updated some terminology for all of our products to use “Feature” (instead of default Master Feature), “Epic” (instead of default Feature) and “Story” (instead of default Requirement). Unfortunately, this update in terminology isn’t consis...
Kirstin Maurer about 6 years ago in Account settings 0 Future consideration

Make the terminology around "Organization" customisable

Across most of Aha! you are able to re-name key items, such as Objectives, Epics, Ideas etc... this is great as it helps you align to the terminology used inside your company. It is not currently possible to do this for Organizations. I believe it...
Dan Jeffery over 2 years ago in Account settings 0 Future consideration

Custom Fields: Automatically linking the values of one field to be published in the linked field

I have created a custom field in features which links to persona’s. I am able to add the relevant persona’s for the product. The drop down shows the correct products to choose from. Similarly, I have created a custom field in persona’s linked to f...
Project Parker about 7 years ago in Account settings 4 Will not implement

Add a group called "None" to the Paid seats group, right now we have no way to know if someone is in that group

Our instance uses paid seat groups, We have 93 paid seats, and the Account>Billing page shows 80 / 93 in use. However that is not the accurate picture. If you go to the Users page, you can see 13 others assignged to "None" So we have no ilcens...
Guest over 6 years ago in Account settings 0 Future consideration