ADD A NEW IDEA

FILTER BY CATEGORY

Account settings

Showing 488

Ability to bulk edit Tags

When editing Tags list on "Config Tags" page, having the ability to bulk edit Tags (Delete specifically) would be very handy as the tags list could become very lengthy and removing multiple tags (with a criteria e.g. Tag starting with RFP#) takes ...
Guest over 7 years ago in Account settings / Features 8 Future consideration

Re-use custom fields in any item type

It's cumbersome to need a unique custom field for the same data across different item types. It would be more efficient to be able to use a single custom field in multiple item types.
Max Cascone over 5 years ago in Account settings 7 Future consideration

The ability to configure which fields are included in the feature to pdf export

Who would benefit? Customers who are required to share feature documentation with enterprise or large government clients What impact would it make? Ease of hiding internal information or displaying only customer relevant information How should it ...
Megan Sullivan about 2 months ago in Account settings 0 Future consideration

More granular sharing security configurations

Today the security configuration forces an account wide setting for sharing views and presentations.This forces us into a situation where we have a once size fits all approach, which is frequently a problem for bigger enterprises.It would be highl...
Nigel Lawrence 5 months ago in Account settings 0 Future consideration

Determine default Home Page for All Users

When a user logs into Aha!, the first page they see is the page "How Aha! works". Our users are reporting that this is confusing, as they want to navigate to a page within the product itself (i.e. Feature Board or Releases Overview"). Users arrivi...
Matt Howard over 5 years ago in Account settings 8 Future consideration

Ability to add PO functions to a Custom Role

We have recently implemented Custom Roles in our space that bumped the PO role to Contributor + Custom (eliminating the ability to add new product and granting paid seat access, etc - see attached) We would like the ability to change some of the...
Marina Reyna about 4 years ago in Account settings 8 Future consideration

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 3 months ago in Account settings 0 Future consideration

Custom terminology for new "Roadmap" menu

Currently, you can create custom terminology for most of the menu's in Aha and other terminology. I would also like to be able to rename the Roadmap menu (for example to Reports, as this is more meaningful for our company) as the new Roadmap menu ...
Julie Edwards almost 5 years ago in Account settings 7 Future consideration

Automation Rule - Add "Release" as an Action

In my scenario, there are times that a feature is in a given status, and as a result, I would want that feature to move to a different release. For example, If I abandon a feature, I want it removed from a release and put into a parking lot where ...
Jerrold Emery about 1 year ago in Account settings 1 Future consideration

Report on custom fields used in integrations, reports and roadmap views

Today you can identify which layouts and workspaces custom fields are actively used in. However, when looking to manage a large number of custom fields across a large organization, there is no way to determine which integrations are using that cus...
Jeanette Resnikoff 5 months ago in Account settings / Reports 0 Future consideration