Whiteboards

Who would benefit? Teams facilitating large sessions in whiteboards may not want guests to login to access a whiteboard What impact would it make? The process to create a login can be time consuming - especially for some users who struggle with te...

Who would benefit? Aha Notebooks users What impact would it make? Increase storytelling ability when using whiteboards by providing the ability to add in icons/images to flesh out an idea beyond words How should it work? See attached screenshots f...

Who would benefit? It would save a lot of time and reduce the manual effort of PI Planning preparation and event Execution. It will show that Aha is a tool for Portfolio management and also Planning. With extensive current effort of Aha to align t...

Who would benefit? All whiteboard & icon users. What impact would it make? Being able to find desired icons by theme and keyword How should it work? When one types a word, one gets related icons, like it works in Miro, MS Teams or on Emoji DB....

Who would benefit? Aha! admins and PMs What impact would it make? This would help to ensure the relevant types of documents can be open for collaboration How should it work? Currently, document access settings for the workspace allow for edit/view...

Who would benefit? People working alongside a colleague in a whiteboard would be able to easily follow their colleague and easily collaborate and discuss together in a whiteboard. What impact would it make? Makes it easier to work with a colleague...

Who would benefit? Workspace owners who are currently receiving all requests to edit a document from a reviewer. What impact would it make? The request to edit a document will be reviewed and approved more quickly with less noise to owners that do...

When converting sticky notes in a whiteboard to other record types, we don't want users to be able to bypass required field entry for those record types. I have found other areas within Aha! where required field entry can be bypassed when creating...

It would be useful to define default Document Access settings for notes/whiteboards at parent line levels to be inherited down to workspaces instead of needing to make setting changes for each workspace individually

Today, converting a whiteboard object to a record will include the name. However, it would be useful to automatically apply the initiative, epic, or feature default description template on creation.