ADD A NEW IDEA

Account settings

Showing 613

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 6 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 11 months ago in Account settings 2 Unlikely to implement

Allow team leads to manage workspace releases

Engineering managers & team leads sit "in between" Aha! Roadmaps and Aha! Develop. They more than just team owner permissions, but not full workspace contributor permissions. Key use cases Team leads can provide initial estimates on features b...
Jeff Tucker almost 2 years ago in Account settings / Development / Releases 0 Future consideration

Automation rules API

Hi team!Automation rules help us assign to-dos for our launch readiness process. This works great for tracking work, however, it's a challenge to ensure each workspace has rules in place and that these rules are the same. We would love the ability...
Shawn Zenz almost 4 years ago in Account settings 0 Future consideration

Allow for Create SSO access when sharing notes and whiteboards

As a large organization, SSO is required to access authorized tools. When sharing documents (notes/whiteboards) today with a non-Aha! user in my organization, that user would need to start a free Aha! Create account with a UN/PW or Google SSO. We'...
Jeanette Resnikoff almost 2 years ago in Account settings / Notes / Whiteboards 0 Future consideration

Separate Scorecard for Epics

I would like to know if there is a way to establish a scorecard for Master Features that is separate from the scorecard used for Features. We would like to use a specific scorecard at the Master Feature level such as estimated revenue, cost saving...
Matt Howard over 5 years ago in Account settings 3 Future consideration

Capacity for teams: API support for team schedules

Ability to create and update schedules via the API. This would allow us to automate team availability (user's PTO or maternity/paternity) and easily update company holidays.
Nathaniel Collum over 4 years ago in Account settings / Capacity planning 0 Future consideration

Allow Reviewers to update existing rows in custom tables

We would like to implement Custom Tables in Releases to collect cross-functional status information from different functional/project teams involved in each release. These teams are not part of product management and would only use Aha! to update ...
Ashton Tsou 12 months ago in Account settings 0 Future consideration

API Access Logs

As an admin, we are addressing logging and monitoring policies in our company. We would like to capture a log of API calls made to a specific Aha instance. We are aware that you have an activity webhook that will notify our system of every change ...
Victoria Morrella almost 4 years ago in Account settings 1 Future consideration

Required fields to be excluded from features in the parking lot

Required fields cannot be excluded from features in the parking lot currently. However, it would make sense that if you have a feature under your parking lot is because you still have to define certain things and you may not count at that time wit...
Guest over 4 years ago in Account settings 0 Future consideration