Allow to define default sub-menu to go when menu bar is clicked
For example, every time I click on the Feature menu, it goes to Board section as default. The application could allow the Owner to define inside Navigation configurations what is the default section of that menu. So when I click in Features menu, ...
Fabio Brito
about 5 years ago
in Application
0
Future consideration
"Mark all read" should not mark new notifications not yet displayed.
So I was on the notifications page and, after reading the notifications and doing stuff based on them (and taking a phone call, etc.) I went back to click "Mark all read". As my finger hit the button, I saw the "New Notifications" alert. Unfortuna...
milestones shouldn't have a progress bar when field is selected for reports
When creating a pivot table of release phases & milestones, adding the "progress" field to the report shows a blank progress bar for milestones. since milestones don't have an option for progress tracking, the progress bar shouldn't appear for...
David I.
over 1 year ago
in Reports
0
Future consideration
We create a product maturity grid along with a product vision that includes MVP (minimal viable product), enhance and compete. Our capabilities are linked to these categories.
The product maturity grid allows us to determine our product maturity b...
Guest
over 8 years ago
in Strategy
2
Already exists
Product is consistent color carried throughout all Aha! record objection and reports
We report (Aha! presentation) multiple products to our business partners/owners through custom roadmaps, notes, list and other aha! report types. When you use multiple report types in a single presentation, we use color to separate content by prod...
Guest
about 5 years ago
in Presentations
0
Unlikely to implement
I am creating a presentation for a product release which contains many features split across different functional components. I've created a Pivot view that I like, which breaks down the features by component. But it's too long for one slide. I'd ...
Rich Baldry
over 3 years ago
in Presentations
0
Future consideration
Currently when trying to report on the record number, it's name differently across all records. Can you please choose one naming convention to improve UX.
Initiative: Reference #
Release: Reference
Feature: Key
Requirement: Reference #
I person...
Guest
over 5 years ago
in Reports
2
Already exists
We want to use Aha! as the sole source of truth for competitive analysis and assessment. It would be very useful to be able to perform CSV imports like other parts of the data model. We understand that Aha! supports data entry and exporting throug...
Guest
almost 9 years ago
in Strategy
0
Already exists
In Jira integration 2.0, there's no link or reference to the items created by the integration once you approve them.
A modal notification like you currently use would work at a one-by-one level. If that makes sense.
Even better would be a tab in ...
Max Cascone
about 7 years ago
in Jira
1
Future consideration
Story
As a PM, some uncompleted Feature cards become outdated and would be best revised back down to Ideas.
Case
A bulk manage tool that downgrades Feature cards to Ideas would be very useful. Potential field mapping could be presented to the user...
Guest
almost 9 years ago
in Features
3
Already exists