ADD A NEW IDEA

Features

Showing 1148

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

Confirmation for bulk update or delete options

While someone is doing a bulk edit or delete, you can show a warning or alert on the middle of the screen highlighting the bulk update or delete to avoid accidental updates.
Guest almost 3 years ago in Features 0 Future consideration

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

Create competitive pricing tier for low-access users

Picture this. You're paying Aha $1800 per year for Enterprise+ because that's the tier you need. 100 people work at your company, and they have been using Zoho Projects @ $60 per year per person. You are not not not going to convince this company ...
Debbie Levitt almost 3 years ago in Features 0 Will not 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

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

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 over 8 years ago in Features 0 Unlikely to implement

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

Add ability to import requirement comments when importing a feature

Requirements can be imported as part of the feature import from CSV routine. The requirement comment field is not included in the possible fields. Aha! users need to be able to keep track of the comments that are being imported and so at the momen...
Steve Dagless almost 3 years ago in Features 0 Future consideration