Skip to Main Content
ADD A NEW IDEA

Features

Showing 734

Default rows in custom tables

I would like to be able to create default rows/values in a custom table. For our use case, we would like a table for DoD which includes several default values from a drop down in a row (i.e. Acceptance Criteria Met, Testing Requirements Met, etc) ...
Guest almost 5 years ago in Features 1 Future consideration

JIRA to Dynamically Update Features' Phases in GANTT Chart

For those using JIRA Cloud integration, it would be helpful to have features move between the Gantt chart phases automatically based on JIRA status changes
Guest about 2 years ago in Features 0 Future consideration

Allow to arrange custom fields in two columns

Currently each custom field, e.g. in Feature detail is listed in an extra line. The fields are very short, so a lot of unused space is wasted right of the fields. It would be very helpful to arrange the custom fields the same way like it is possib...
Alexander Vukovic over 6 years ago in Features 1 Future consideration

Bulk edit note custom fields

Our companies uses a few custom fields as part of our features. All of the custom fields that we use are notes. Enabling note-type custom fields to be bulk edited would be extremely useful.
Guest almost 5 years ago in Features 1 Future consideration

Ability to sort feature cards in a release according to default priority ranking field

A product manager will frequently switch between the priorization screen and the board to view features. If the drag-and-drop stack ranking is used and without product value, then the card sorting drop-down excludes this field. The workaround is t...
Guest 9 months ago in Features 0 Future consideration

Lower Shipped Epics in Drop Down Lists

After you've been using Aha! for a while, the number of epics builds up. This can be come a hinderence when you are looking to add a feature to an epic and the drop down list has dozens of results. After speaking with Aha! engineers, it was pointe...
Guest over 3 years ago in Features 1 Future consideration

Change scorecards without erasing scores

Currently, selecting a new scorecard will erase all existing scores. The manual workaround is to export all your scores and re-import them again after changing the scorecard, but this is very tedious and non-obvious. Instead, allow the user to map...
Todd Meyer almost 3 years ago in Features 0 Future consideration

Allow feature board to be sorted by start or end date

We're having trouble keeping the board and gantt in sync in terms of order, because they don't really share any sorts (except rank, which we're not currently using) - so anybody using stack rank to prioritise in board or gantt have to duplicate work.
Guest over 4 years ago in Features 0 Future consideration

Archive Table fields/rows/columns to save historical data

When using tables to capture historical data, we need to archive past data so we can remove columns/rows to clear up the view but not lose the data in the cells. For instance, we are capturing costs and benefits by year, 2019, 2020, 2021, etc. Nex...
Laura Spohn over 4 years ago in Features 0 Future consideration

Import from CSV - Be able to update existing requirements like you can features

The Import from CSV utility allows for you to perform import updates to existing features by referencing the Feature ID. It would be highly desirable to be able to do the same with existing requirements that are part of the same feature by keying ...
Matt Case about 7 years ago in Features 2 Future consideration