ADD A NEW IDEA

Features

Showing 1169

Add Jira "status" field

When working between Aha and Jira, it can be hard to tell what is being updated in each. It would be helpful to have a Jira "status" field that allowed us to definitively see the status.
Guest almost 9 years ago in Features 0 Unlikely to implement

Security per Feature or per Release

To enable consultants and freelancers to also provide estimates and work using Aha!, please implement more fine-grained security features to add user and choose from a list of features they are allowed to see and contribute. This is critical to en...
Guest almost 6 years ago in Features 3 Unlikely to implement

Improve "Move requirement to another feature" dialog to help quicker find the required feature

Currently, if I need to move a requirement from one feature to another, I need to remember my destination feature name, and even then there could be several with the same names. Would be good to see and be able to search by more context, for examp...
Laisvune Valackaite almost 6 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

Seat assignment permission should be separated from billing

Assigning and un-assigning seats is weekly task as we have product and dev members joining and leaving. Upgrade subscription is quarterly or longer term task as it depends on budget. In my opinion the first task should not require billing permiss...
Guest almost 6 years ago in Features 0 Already exists

Behavior of bulk edit product permission "to none" is not consistent with "from none"

When bulk edit product permission to viewer or product owner for example, product line permission of "none user" will change to the new value accordingly while other users will keep their their individually assigned permissions. This is a desirabl...
Guest almost 6 years ago in Features 0 Future consideration

Choosing Fields to Import

The Aha Link being visible in JIRA is crucial for us so Engineers can click over to Aha for more info. However, when you link with an existing ticket, there is no way to just send the Aha link. You should be able to pull in specific fields &...
Guest almost 6 years ago in Features 0 Future consideration

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

Missing Avatar image Url for assigned_to_user in feature API

For features API we are getting two objects 1) Created by user 2) assigned to user Both the objects are having same attribute except assigned to user is missing Avatar image Url. We need feature owner image so we can flow it to other integrations.
John T almost 6 years ago in Features 0 Future consideration

Filter out unlicensed re/viewers from Workflow board configuration

The workflow screen functionality is only accessible to licensed users, so it seems distracting to display and have the opportunity to check them (or have to uncheck them), and even less useful to display them on the screen. I'm not sure that I wo...
Guest about 9 years ago in Features 1 Future consideration