Features

Showing 575

Have workflow status change dates refelect the most recent date a status was set

The value of “Status changed to <status X>” for a feature workflow appears to perpetually contain the date of the first time that the status was changes to <status X> rather than the date of the most recent transition to <status X&g...

David Kettinger over 8 years ago in Features 6 Future consideration

9 VOTE

Scorecard automated metric should allow you to select other scorecard fields

We have implemented two separate scorecards for feature cost and feature impact. This gives us more flexibility in reporting/filtering based on what-ifs. We would like to combine those two scores in an an overall feature score to use for prioritiz...

Rich Baldry over 2 years ago in Features 0 Future consideration

9 VOTE

Copy features into new workspace

It's currently possible to create a new release in a new workspace that is a copy of a release in another workspace, which will also copy all of the features within that release. If I need to copy a single feature to a new workspace, though, I hav...

Finn Meyer over 2 years ago in Features 1 Future consideration

1 VOTE

Milestone Dates: Could we introduce a feature that retains the original milestone date, but also displays an arrow and a new icon when the date is changed?

What is the challenge? if the milestone date has changed, our team wants to be able to see both the old and new date. What is the impact? unable to see the date change when a project gets delayed Describe your idea have an icon for the original da...

Guest 3 months ago in Features 0 Future consideration

15 VOTE

Option to expand all requirements on a feature

In the old Aha! design there was an option on a feature to expand all the requirements. This was great for quickly showing all the links to Jira. Could you bring this option back?

Kelly Sebes about 4 years ago in Features 0 Future consideration

10 VOTE

Rename product value field in non-product workspaces

The product value score terminology works well for workspaces where teams are building products. But in other workspaces it can be confusing. In these cases a more generic field name would be easier to understand.

Austin Merritt almost 3 years ago in Features 1 Future consideration

19 VOTE

Allow multiple workflows in a product

Within a given product there can be different types of initiatives and features. Aha! supports the concept of feature types and allows templating of the description field by type. Would like to see an expansion of this concept to support configura...

Bonnie Trei over 5 years ago in Features 5 Future consideration

3 VOTE

Roadmaps status displayed on requirement in Develop is confusing

What is the challenge? Currently the collapsed view of a requirement under a feature in Develop will display it's Roadmaps status and not it's Develop status (example attached) What is the impact? This can be very confusing when managing requireme...

Chris Quigley 10 months ago in Features 0 Future consideration

30 VOTE

Aha should delete the integration link when receiving a delete trigger from a webhook

We have Aha linked to JIRA. When we delete an issue in JIRA, this triggers our Webhook to send a message to Aha. I understand and agree that this should not cause Aha to delete the Feature connected to it for security reasons. But I would expect A...

Marvin van Dongen over 8 years ago in API / Features 8 Future consideration

12 VOTE

Allow features to be grouped by epic in feature board and feature workflow

Currently, there is no grouping available in feature board. In feature workflow, it is possible to group by assignee. It would be great to be able to group both views by epic.

Joao Tornovsky over 3 years ago in Features 0 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY