All ideas

Showing 9093

Default admin responses for each status

As a Product Manager, when I change an idea status, I want a default admin response to appear automatically. I could then tweak this pre-populated response as necessary and publish it. This would save me a lot of time during our idea triaging sess...

Elina Hu over 8 years ago in Ideas 2 Future consideration

5 VOTE

Scope / granular permissions for API Access

Hi All, currently every user with Aha! access can create an api token or authorize Apps to use the Api. And the Scope is tied to the user itself and not configurable. When it comes to projects, utilizing the API, it is the Application Owner / Admi...

Oliver Berger over 1 year ago in API 0 Future consideration

4 VOTE

Add Support for Workspace Rules in Automations

Who would benefit? All users What impact would it make? We currently have custom fields at the workspace level and would like to be able to create automations based on when those fields are changed. For example: We have a custom user field "Progra...

David Willequer about 1 year ago in Application 1 Future consideration

25 VOTE

Velocity-Based Planning

We'd like to estimate and plan releases based on velocity (rate of story point completion) rather than capacity (static value). This would enable more dynamic calculation of release capacity given a target release date and velocit(ies) over the d...

Guest about 7 years ago in Capacity planning / Releases 2 Already exists

3 VOTE

Order / Distinguish Workspaces in Users CSV Export File

Who would benefit? Aha admins and workspace owners who would like to get user access information from the users csv export file. What impact would it make? Easier to find relevant information from the csv file Admin is able to develop script to tr...

Hank Liu 11 months ago in Account settings 1 Future consideration

15 VOTE

Sync releases for Azure DevOps integration

Currently we cannot push work back from Azure to Aha correctly as the releases/Iterations do not sync which causes manual work to move a card to the correct Aha release once imported. Iterations can be nested in ADO, and when you try to send recor...

Ronnie Merkel over 4 years ago in Azure DevOps Services and Server 0 Future consideration

2 VOTE

Make it easier to find the report I need and create them consistently

What is the challenge? Users find Aha! reporting tough to navigate and tough to create reporting consistently. What is the impact? This leaves users with a negative opinion of how easy Aha! is to use for reporting and thus they use it less. Descri...

Deirdre Clarke 7 months ago in Reports 0 Future consideration

2 VOTE

Allow more control of report/roadmap formatting and a direct integration with PowerPoint

What is the challenge? Reports and roadmaps created in Aha! are not in a good enough format to persuade senior leaders to look at them. What is the impact? Which makes the roll-out of Aha! a vicious circle – senior leaders don’t want to see the re...

Deirdre Clarke 7 months ago in Reports 0 Future consideration

9 VOTE

Aha! Develop - Reopen a completed sprint

It is possible to re-open a shipped release to make changes that should have been included. The same logic should apply to sprints as there are various reasons I may need to make changes.

Dale Potter over 2 years ago in Sprints 2 Future consideration

21 VOTE

Fix critical Aha to VSTS Integration not syncing Feature Order

We are trying sync the Feature order from Aha to VSTS (never the other way around). Keeping the Features in VSTS in the same order in Aha is in our use case, critical to using the integration. The reason that it fails is because matching the Aha R...

Guest about 6 years ago in Azure DevOps Services and Server 2 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY