Skip to Main Content
ADD A NEW IDEA

Account settings

Showing 60

Record level permission restrictions

What is the challenge? Some features or initiatives are sensitive, so we would like to be able to set record level permission restrictions What is the impact? Anyone who might come across work that isn't being widely publicised in the org Describe...
Nerissa Muijs 3 months ago in Account settings 0 Unlikely to implement

Ability to set a specific date in automation rules

Who would benefit? everyone What impact would it make? high priority for our key product team In the area in setting an Automation Rule you can set dates for things like 1 day or 1 week from today. Our team wants to enter a specific date to be set.
Leanne Miller 9 months ago in Account settings 2 Unlikely to implement

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

Removing Additional Checkbox on Workflow Change Box

When making a workflow change to any object in Aha, users are prompted to select a box and then make an additional checkbox selection. While this button click is a nice control, it is an extraneous user click and may create UX dissatisfaction.
Josh Tambor over 4 years ago in Account settings 4 Unlikely to implement

Once user is registered in Aha!, they should be able to easily see what they have access to

We don't provide access to the Aha! portal to our customers. Customers are only provided access to our roadmaps through Notebooks. When I add a customer as a user on Aha! and provide them access to a pseudo product which has access to the roadmap ...
Amol Naik about 5 years ago in Account settings 1 Unlikely to implement

Share Editable Choice custom field data across record types

Our Product Managers use required to define multiple key results per outcome. To capture this information we have implemented a custom field using the Editable choice field type. When A product manager creates a release, we would look to be able t...
Andrew Brooks over 5 years ago in Account settings 0 Unlikely to implement

Workflow - option to view based on assignee as well as a "custom" tag/ field that identifies a development team

Product Owners are assigned the feature and then work with multiple teams, it would be great to see the workflow based on the assigned but then also the split of teams
Natasha Venter over 5 years ago in Account settings 1 Unlikely to implement

Advanced product permissions for users

I like that Aha! allows me to share my product data with my organization, but I need more granular controls over who can create, read, update, and delete data. It would be great if I could create custom roles and assign them to users. Additionally...
Nathaniel Collum over 5 years ago in Account settings 1 Unlikely to implement

Log time without requiring a full priced license

I love Aha and I think it is worth the money we spend on it, however, there is a gap on the license model x functionalities provided that prohibits me to fully adopt it for my dev team (9 developers), eliminating Rally. The request here is to cre...
Moises Cora over 5 years ago in Account settings 1 Unlikely to implement

Disable custom fields, tables, etc. so they can be seen where previously used, but aren't available for continued use

As explained above. It will help when a custom field is deprecated, but new users don't realize they shouldn't use it.
Guest almost 6 years ago in Account settings 0 Unlikely to implement