Showing 898 of 6046

Option to expand all requirements on a feature

In the old Aha! design there was an option on a feature to expand all the requirements. This was great for quickly showing all the links to Jira. Could you bring this option back?
Kelly Sebes 8 months ago in Features 0 Future consideration

Shift-Enter Keyboard Shortcut from Requirement Description field starts a new Requirement

As a product manager trying to achieve flow despite my ADHD, I need to be able to keep my hands on the keyboard when cranking out my GWTs so that I can work fast and not get distracted.Given that a user is creating a new Requirementwhen the user i...
Guest about 1 month ago in Features 0 Unlikely to implement

Inherit field values from Epics to Features

By default, have the Epic based data values copied over to the Feature data fields when the user creates a new feature from an epic card. This eliminates the need for re-entering and possibly inconsistent values for the same fields. If inherited f...
Guest 5 months ago in Features 2 Future consideration
126 VOTE

Link "ideas" portal comments to promoted "features"

When one promotes an "idea" to a "feature", the comments for the "idea" remain in the "idea" and don't move to the "feature". It would be very helpful if the features from an "idea" would seamlessly be available in features (even if it were just ...
Guest over 6 years ago in Features 17 Future consideration

Kanban Board - Custom Swimlanes

Currently swimlanes are by owner which is helpful when micro-managing resources however we group resources into teams and focus features on given teams. It would be nice to support custom fields/groupings on the swimlanes so I could choose how i w...
Thor Taylor almost 5 years ago in Features 22 Future consideration

Estimate in allocation percentage

I want the ability to estimate in allocation percentages. Fo example: I'm planning 2H 2020 feature planningI want to say that 50% of Sally's time is dedicated to a specific initiative. I want to create that initiative, give it a date range of 2H, ...
Guest over 1 year ago in Capacity planning / Features 1 Future consideration

Global Prioritization of Features

As a product manager who manages multiple products and has a development team working with multiple productsI would like a straightforward way to prioritize features across productsSo that I can communicate to my developers what our highest priori...
Daniel Schwent over 2 years ago in Features 3 Future consideration

Automation for epics/features at the parent line level

As a portfolio manager, I want to create a single rule for epics/features for all workspaces in a parent line. Right now I have to recreate these individually at the workspace level. Part of the problem is the amount of time it takes to create eac...
Nadim Sobhani 4 months ago in Features 0 Future consideration

Assign individuals to work using % allocations

We need an ability to assign one or more individuals to an Aha! record and indicate that their capacity is partially allocated to that record.For example, initiative A is estimated at 1,700 hours and assigned to Team A. User A on the team is assig...
Mark Eaves about 1 month ago in Capacity planning / Features 0 Future consideration

Copy requirements

It would be helpful if we had the ability to copy a requirement to the same feature. We use requirements as product backlog items. Sometimes they are too big. It would be useful to be able to copy a requirement as the first step in splitting it.
Tom Beck over 3 years ago in Features 3 Likely to implement