ADD A NEW IDEA

Features

Showing 230

prioritization view

my team currently has a ton of stuff in the parking lot - but it is very tough to prioritize this because the card-based layout is frustrating to use when you're only moving up/down in one column. too many other things and a lot of weird scrolling...
Steven Kaplan almost 8 years ago in Features 1 Already exists

Drag and Drop in Bulk Feature for Conversions

Introduce drag and drop feature (in bulk) for converting features into master features or mater features into regular features. This will save time and allow bulk actions for imported data and when manipulating multiple feature cards in correct hi...
Guest over 2 years ago in Features 0 Already exists

Filter by Product or Feature Board When adding new Feature/Master Feature

Give users option to filter by all products or current products/feature boards when adding new feature or master feature (why scroll through all irrelevant items). This will save time and make it more user friendly.
Guest over 2 years ago in Features 5 Already exists

Remove Deleted Features from Database/Drop Down Menus

When you select a feature from drop down menu, even if previously deleted--it allows you add greyed out features. Why not archive them completely? It still allows for user to accidentally add the “deleted” greyed out item causing errors.
Guest over 2 years ago in Features 3 Already exists

Status filters on products should only match the available status workflows for that product

Currently, all available feature status workflows appear when I select the filter by feature status in my products...including the default system workflows which are assigned to none of my projects. This is a frustrating UX experience - the on...
Guest over 5 years ago in Features 0 Already exists

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

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

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

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

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