ADD A NEW IDEA

My votes: Account settings

Showing 46

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 15 days 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 6 months ago in Account settings 2 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 about 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 almost 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 over 5 years ago in Account settings 0 Unlikely to implement

Floating License

We have around 10 users that need to use AHA! but only 6 that generally ever need to use it concurrently. Right now, we accomplish this by activating/deactivating accounts as needed. It would be great if the user licenses tracked user concurrency,...
Oleg Yazvin over 5 years ago in Account settings 1 Unlikely to implement

Object level Security

Provide the ability to assign contributor roles to specific Master-Detail custom tables- at the table/object level. This would allow access to be limited to just specific areas a user is responsible for- instead of across-the-board editing. We wou...
Jana Decker almost 6 years ago in Account settings 1 Unlikely to implement

Allow Requirement Dates to drive that roll up to a Feature to drive that Feature's start & due date.

We integrate with Jira Engineering work at the Requirement level and must see dates associated with Jira Stories as Requirements in Aha! Since addressing the Requirements / Jira User Stories make our Features a reality, we request that a setting b...
Guest almost 6 years ago in Account settings 4 Unlikely to implement