Initial estimates -option to change the default to support parallel planning
Currently the initial estimate defaults to the number of days between the start and end date of an EPIC (and feature). At the EPIC level this can through off our capacity planning if the advance estimates are not updated when the EPIC is created. ...
Ruth Gardiner
11 months ago
in Capacity planning
0
Future consideration
Make popouts in embedded Aha! views in Confluence larger for easier visibility
When embedding an Aha! view that allows drilldown in Confluence, the popout boxes for the drilldowns are relatively small and make it difficult to view all of the content. The same popouts in a webpage or fullscreen view have a lot more room and m...
Maria Plotkina
11 months ago
in Integrations
0
Future consideration
Be able to search documents in the main search bar
As a user, I reference several internal documents and templates to do my work in Aha. I would like to be able to search for all record types (Initiatives, Features, Epics, Documents, Attachments) in the same search bar.
Guest
11 months ago
in Search
0
Future consideration
A simpler, more modern UI and UX for Aha would make it easier to adopt across different teams in the organization as a sole-source of truth while at the same time making it easier and more efficient to work with Aha. Some key areas and KPIs includ...
Victor
almost 2 years ago
in Application
1
Future consideration
We have SLAs in place to make sure we respond to ideas in a timely manner so it would be good to easily track the number of days between an idea being created and the first public comment being left on it. There is a column for public comments but...
Peter Whisenant
almost 2 years ago
in Ideas portal
1
Future consideration
The search functionality is pretty terrible, but a very important feature to have done right as it prevents duplicate ideas from being created and has the potential to save a ton of time and headache. Currently, search requires that you enter exac...
Guest
almost 3 years ago
in Ideas portal
1
Future consideration
Automatically numbered headings in the description
For longer Epic/Feature descriptions, having numbered headings makes it easier to read and refer to specific parts of the description. I would like to have automatically numbered headings, so I don't have to do this manually, and if I add a headin...
Martin Haitsma
almost 3 years ago
in Epic
0
Future consideration
I would like to crop reports that have been added to a notebook. Some of the reports that I send to the notebook have an excessive amount of white space which makes it difficult to use the notebook space efficiently.
Codi Gaudreau
over 5 years ago
in Presentations
1
Future consideration
We would like the ability to configure the feature “Aha! Score” at the product line level
Currently, it only appears to be available by updating the “Scorecard for features” product by product. It would be helpful to be able to setup score cards at the Product Line and have them inherited by the products within the product line.
Mike Jacobson
over 4 years ago
in Features
0
Future consideration
Would like to track when a feature was sent to JIRA and by who? Can you please let me know how I can accomplish this?
JIRA_KEY (I am able to pull)
JIRA_KEY_CREATE_DATE (Not known)
JIRA_KEY_CREATED_BY
Thank you
//Need this for SOC compliance//
Sasi Ravichandar
over 4 years ago
in Jira
0
Future consideration