All ideas

What is the challenge? When a to-do is assigned to multiple approvers, if the first approver rejects the to-do, the remaining approvers are unable to respond to the to-do. What is the impact? The remaining approvers do not have the option to provi...

We want to automate the documentation of all of our integration points (integration to Jira). We would like to see not only the integration name, rather we would like to see the specifics field mapping information , direction of integration etc...

What is the challenge? When viewing the Epics on a board view, a capacity line does not appear even when "Epics" or "Features and epics" are used for the calculation. What is the impact? When estimation is done at the epic level, and epics are use...

What is the challenge? Our organizations have custom fields that are also segment groupings. Our industries wish to be able to view by organization (proxy votes view in the portal) but also have the ability to filter by segment. This is not poss...

What is the challenge? The Now/Next/Later roadmap provides an option to use the release date internal field to determine the column groupings and to display on the card. The external release date is not supported on this view. What is the im...

What is the challenge? We have to extract excel report of each shipped release records and save in sharepoint, lots of manual efforts in maintaining logs of each change in release (change in scope-addition/removal of features and epics when rele...

What is the challenge? i do not want customers to see merged ideas in the portal. it is possible to hide merged ideas in the portal, but not in an automated way. i either have to a) pull a report of all merged ideas, and make sure the portal vis...

Who would benefit? Users that: need to track upstream work they are dependent on need to understand downstream work that is dependent on their work need to easily identify delivery risks based on dependencies What impact would it make? A roadmap i...

What is the challenge? We use the 'Note' field throughout our record types, including Goals, Initiatives, Features, Requirements, etc. While we can use To-Dos, it would be easier for many of our use cases to @mention someone directly in the field ...

What is the challenge? Currently, the "Created By" field on the idea card in Aha! displays only the name of the user who submitted the idea. However, this information is lost when the idea is promoted to a feature/epic, making it difficult to trac...