ADD A NEW IDEA

Features

Showing 1157

Configuring workflow board should be reflected for all users

Currently, if I was to configure the feature workflow board (and/or feature cards on workflow board), the changes I made would only be reflected back to me. Every user of the workflow board has to then configure the board (and/or feature cards) th...
Guest over 5 years ago in Features 2 Already exists

Status color legend on the features board

Feature cards on the features board are colored based on their status. When stakeholders, such as leadership, are browsing the features board, they may not know how the statuses correspond to the color of the feature cards. It would be helpful to ...
Matt Bilan almost 3 years ago in Features 0 Future consideration

Feature dependencies based on Requirement dependencies

Our engineers have a good view into Jira issue dependencies. Our business process enforces that all Jira issues will belong to a Jira Epic. We then map those Jira Epics into Aha Features. We would like the Jira Story/Task/Bug dependencies to be ro...
Alfred S almost 3 years ago in Features 0 Future consideration

Ability to NOT include the Description Field for the Create Template

I am using the new Template capability to provide guidance for populating Initiatives / Capabilities (Features) via a standard format. Unfortunately, to use this feature I am required to include the Description field in the Create Layout. This res...
Peter Bongiorno almost 3 years ago in Features 0 Future consideration

Make it easy to move features from one product to another, or create a dependency in another product

We have master and child products (platforms and products built on the platform). Often times, we have a feature in a child that requires updates to the platform. to do that we have to navigate to another product, add the feature, go bck to the ch...
Guest over 8 years ago in Features 0 Unlikely to implement

Planing layer

Hello, we are working at this moment from Calendar view, with a number of features per day. That works great for features requiring less than a day to get finished. But to plan on larger features, it shoud be nice to have a planning system on top ...
Guest over 5 years ago in Features 0 Already exists

Permission for Scorecard so that a seperate party can control one part

It would be great to allow a VP of Sales to be a reviewer and have control of the "Sales" section of my scorecard. If you take that logic and expand, I could have Services / Support / Marketing all managing their own scoring, but still control the...
Guest over 8 years ago in Features 0 Unlikely to implement

Bulk selection of features

When looking at a feature list one can only select a multiple features by either marking 1 by 1 or selecting all. In would be great if it was possible to bulk select features by marking one and then by clicking SHIFT + another feature, all the fe...
Guest over 8 years ago in Features 0 Unlikely to implement

Remove Epic as mandatory field while a feature is created.

To create a feature I must link it to an Epic before I can save it, but then I can go back and unlink the Epic. If I can go back and unlink the Epic, then why not allow the user to create a feature without linking it to a specific Epic from the be...
Guest almost 3 years ago in Features 0 Already exists

When creating a new Feature in Aha! and pushing the data to Jira: Aha! should have a way to handle sending data to Jira fields which are: a) required b) Autocomplete Renderer so the Epic can be created and not rejected by Jira

I created a new feature in Aha! When I attempted to send the changes from Aha! to Jira, expecting a new Epic to be created in Jira, I got the following error: The following required fields could not be set on the epic: Fix Version/s. Please check ...
Guest almost 6 years ago in Features 8 Already exists