Skip to Main Content
ADD A NEW IDEA

Features

Showing 1146 of 8643

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 over 5 years ago in Features 8 Already exists

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 over 5 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 over 5 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 over 5 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 over 5 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 over 5 years ago in Features 0 Future consideration

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

Hover Bulb for Feature Cards

With numerous features for an enterprise program, it becomes hard to use even the "small" card in the Feature Board. It is best to provide a "single-line" card, with hover text showing full details of each feature. Without this, backlog grooming i...
Guest almost 6 years ago in Features 0 Future consideration

Feature Layout Bottom Section Customization

Hello! I've added some quality management fields to the bottom of our feature record since the admin section allows you to have fields at the top or bottom. However, it doesn't allow me to update the title and only calls the section " Custom Field...
Guest almost 6 years ago in Features 0 Future consideration

Milestone markers on features board

I'd like to put milestone markers on the features board, so I can call out important, um, milestones, in the product's journey. It'd be great if they could be dynamically linked to the release milestones. Somewhat related to APP-I-794.
Max Cascone almost 6 years ago in Features 0 Future consideration