ADD A NEW IDEA

Account settings

Showing 636

Add more specificity/granularity around automation logic.

Who would benefit? Both Aha! administrators and the product team members they support through administration of the tool. What impact would it make? It would allow Aha! administrators to automate actions and notifications that advancement can be m...
Christina D 12 months ago in Account settings 0 Future consideration

Have workspace templates be default for new workspaces

Who would benefit? anyone who administers an aha account What impact would it make? streamlines work, reduces chance of manual error, reduces need to manually verify items How should it work? allow account admins to set what the default workspace ...
Guest 12 months ago in Account settings 0 Future consideration

When updating our Aha! account domain we need embedded links to records in Aha! that reference our old domain to continue to work

We are considering updating our Aha! account domain and would like for links embedded in our Aha! records that reference our old domain to continue to work to provide continuity for our team. Manually updating these links is very time consuming.
Erin Ward over 1 year ago in Account settings 2 Likely to implement

Consider inherited values when copying workspace settings for workspace templates

Who would benefit? Any users creating a workspace template from an existing workspace. What impact would it make? Today if a workspace template is created from an existing workspace, Aha! does not look at inherited settings. For example, at the wo...
Kristina Gass 12 months ago in Account settings 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 almost 6 years ago in Account settings 3 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

Develop team owners should be able to manage team members

Who would benefit? Team owners that do not have the customization admin role What impact would it make? Currently Develop team owners do not have a place in the team settings to manage the users in their team, but this is a permission owners have ...
Jason Gillmore 12 months ago in Account settings / Development 0 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 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

Bulk edit "custom table relationship" custom fields

Bulk edit is not currently available for "Aha! record relationships" custom fields, nor "custom table relationship" custom fields. Adding the ability, at least for "custom table relationship" custom fields will go a long way to increasing usabili...
Guest almost 6 years ago in Account settings 0 Future consideration