Skip to Main Content
ADD A NEW IDEA

Account settings

Showing 513

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 about 4 years ago in Account settings / Capacity planning 0 Future consideration

Business model canvas for customer data

Who would benefit? Product manager and Customer success manager What impact would it make? a page with clear data on each customer How should it work? Customer data in a templatized format will give a handy info to product manager and everyone in ...
Guest 6 months ago in Account settings 1 Future consideration

Be able to select a default scenario for all users (Capacity Planning)

Right now, when you add a new scenario (even if it is just a test scenario), all users will be defaulted to that new scenario. We will have dozens of people using the tool, so the inability to get them to all set their own defaults to our standard...
Megan Sanders about 3 years ago in Account settings / Capacity planning 0 Future consideration

Ability to Further Control Notifications

I currently get notifications from Jira when issues/features I have created or am watching get updated. I then get the exact same updates from Aha! for these same issues, causing a frustrating duplication. The issue is, there is no way to change t...
Guest 11 months ago in Account settings 0 Future consideration

Custom Fields Permissions

When creating custom fields for ideas or features we need ability to select which user group has rights to edit it. We created a field named owners, with multiple select options from which a product owner can select several names of people that ow...
Guest over 9 years ago in Account settings 6 Unlikely to implement

User Report - Additional Filter - Last Activity

Being that we don't have a reliable user access management tool, our Admins clean up the users if no activity after 90 days. Unfortunately, there isn't a way to filter this, so I must click every user on the page in order to disable in bulk. Click...
Victoria Morrella about 3 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 about 4 years ago in Account settings 0 Future consideration

Ability to vary a team's cost by calendar year

A team will have a defined cost that is applicable for the calendar year. When putting together a multi-year plan, there needs to be a way to account for factors that will cause the team's cost to increase (e.g. inflation). There needs to be an ab...
Mark Eaves over 3 years ago in Account settings / Capacity planning 0 Future consideration

Preserve history when converting from one object type to another

Currently when an object is converted to another object type from within Aha! the history is cleared on the new object (Initiative to Master Feature, for example) From an audit and logging perspective it would be preferable if the history was pres...
Justin Woods about 6 years ago in Account settings 1 Future consideration

Ability to set whether a custom number field is allowed to be used by the prioritisation board

Who would benefit? All users What impact would it make? Avoid the potential for data loss How should it work? At the moment, any custom number field that is available on a record's layout is presented as an option to be used to capture the priorit...
Steve Dagless 6 months ago in Account settings 0 Future consideration