All ideas

Showing 9110 of 9110

Allow mapping Release as a field on Requirements in Azure DevOps integration

Due to our iterations setup in Azure DevOps (ADO) we do not currently map Releases as a record. We are sending this instead as a field on the Epic and Feature records to a custom field in ADO. We would like to do the same on Requirements but it is...

Guest over 3 years ago in Azure DevOps Services and Server 0 Future consideration

4 VOTE

Add a new role in Aha that CANNOT create or view reports and roadmaps

This will be useful for a product organization that would like to provide access to teams outside of products but do NOT want those non-product users to create or view reports or roadmaps. Currently, there is no role that prevents users from creat...

Guest over 4 years ago in Account settings 0 Future consideration

4 VOTE

Azure DevOps integration support for designating default Iteration as backlog

Currently the Azure DevOps Services integration supports configuration of the project and the project area. All work items go to the root project iteration level. However, multiple teams may work in a single project and have a different iteration ...

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

4 VOTE

Create Feature Delivery Type field to map to Rally Feature

This field is required in Rally as it is used for Fixed Capacity Billing.

Guest over 4 years ago in Rally 0 Future consideration

5 VOTE

Push mock-ups from Aha! to Jira Draw.io plugin

We create UX/UI mock-ups in Aha!, and I would likedevelopers to be able to see them after the feature is pushed into their Jira backlog. I noticed that both Aha! and Jira use Draw.io for mockups. Is there any way Aha! can upload mock-ups associate...

Guest almost 6 years ago in Jira 4 Future consideration

4 VOTE

Allow for Features to Integrate with Multiple Epics

We have multiple teams working on multiple Epics in JIRA that all track to a single Feature. It would be very helpful to enable integration of a Feature to multiple JIRA items.

Cindy Datlof over 4 years ago in Features 4 Already exists

5 VOTE

Field Level Notifications

As a Product Owner I want to know when a label has been added to the release object. OR As a Technical Writer, I want to know when a feature has needs documentation. Currently, I can make myself a watcher on nearly every Aha! object. However, Ther...

Jerrold Emery almost 6 years ago in Comments / Notifications 0 Unlikely to implement

4 VOTE

Capacity Planning - Hourly rates by Scenario

We update hourly rates on an annual basis. The Teams we define span Scenarios so we need to be able to define an hourly rate by Scenario for a Team. This functionality will enable flexibility in cost reporting and forecasting.

Chris Brooks over 4 years ago in Capacity planning 0 Future consideration

5 VOTE

Colours for custom fields, especially record relationships

When creating custom fields for record relationships, these only are presented as plain grey links. It would be great if these links could be coloured - either by specifically choosing colours, or by programmtically setting colours like with tags....

Guest almost 6 years ago in Account settings 0 Future consideration

4 VOTE

Update mapped initiative field in integration when changing text of initiative name

The initiative field is available in the Jira integration under the Aha! feature record. It works as expected when initially sending the Aha! feature to Jira. (Note: this is not the use case of mapping the initiative record.) However, the mapped i...

Craig Pflumm over 4 years ago in Integrations 0 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY