All ideas

Showing 9116 of 9116

improved metadata rest services for fields

For users trying to interface with the Aha service via the rest services there is a definite lack of available services for fields. There needs to be a way to validate fields being sent to Aha. Currently there are only services that return filed d...

Tim McCaskill over 5 years ago in Integrations 1 Future consideration

2 VOTE

Autocascade release dates

As a Product Manager, I want to be able to add a standard release cadence and if one of my releases gets delayed, the rest of the releases get pushed back as well. For instance, if we have standard 8-week release schedules and one gets delayed by ...

Guest over 3 years ago in Releases 0 Future consideration

4 VOTE

Followers & CRM integration

Hi, Unsure why this doesn't already exist, but we should be able to list followers who aren't in Aha. For example, if using Salesforce, HubSpot, etc., it would be ideal to list contacts who should be following something (feature, etc.) This shoul...

Guest over 7 years ago in Application 1 Unlikely to implement

1 VOTE

Provide "Confidential" as a watermark on printed/pdf roadmaps

We wanted to send a pdf copy of the strategic roadmap to a partner however it would be nice to put a watermark on it so we can identify it's confidential. As a stretch if we could even customize it then we could put the partner's name on it.

Andrew Belo almost 2 years ago in Roadmaps 0 Future consideration

1 VOTE

Promote a requirement as "is a dependency of" instead "Relates to"

Sometimes a requirement needs to be done one sprint before the related feature. So we need to promote it as a feature. The relationship between the new feature and the previous one is created as RELATES TO. This is a problem, as Gantt chart shows ...

Guest almost 2 years ago in Dependencies / Features 0 Future consideration

2 VOTE

Allow Jira-related fields to be included in automation rules

It would be helpful for fields like the Jira key or integration link to be available in automation rules. That would enable my team to create triggers that look at when an integration link is changed or is no longer available.

Katrina Purcell over 3 years ago in 0 Future consideration

2 VOTE

Allow for null Release Date

Currently the release date field is required. But usually when a release is first written up there is no realistic idea for when it might be delivered. For releases that are postponed or of lower priority, the initial entered dates which seemed so...

Brendan G over 3 years ago in Releases 0 Future consideration

3 VOTE

Apply Template when creating Release from the Master Release

When creating a child release from the master release, allow the user to apply a product template to the created release. This will allow the Sub-Release to have all of the steps etc. required. Currently, the user either needs to create the releas...

Stephen Morse over 5 years ago in Releases 0 Will not implement

1 VOTE

Allow link of a requirement to a release (sprint)

We have features that are mapped to a specific sprint, but within that feature, we have requirements (user stories) that could be mapped to two different sprints. The assumption with Aha! is that a feature would be completed in one sprint, which i...

Guest almost 2 years ago in Azure DevOps Services and Server 0 Future consideration

1 VOTE

Promote Notes OR To Dos to Feature

We are trying to bring our Cross functional partners into Aha and would like a way to easily request work from them. We had been copying our Feature and assigning the UX-specific Feature to them. This allows for the details from the Product Develo...

Joanne I almost 2 years ago in Features 0 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY