Application

Sometimes users realize that their initiatives are actually way bigger than what their company deems acceptable size for initiatives. It should be very easy to convert an initiative to a goal. If that initiative includes Epics (Master features), t...

There is a lot of whitespaces between panels or around charts in ideas. The pie chart is half-the possible size of the panel.

We have a field that exists on both our Features and Requirements, and that custom field is being used in our JIRA integration. When creating a new requirement, it would be great to have the field auto-populate from what is specified in that field...

What is the challenge? Currently, when a new idea is linked to a record in Salesforce, the page refreshes. What is the impact? If this happens while the Salesforce user has an open chat or call in the Salesforce interface, this can disconn...

What is the challenge? I have to change the settings to switch to size 12 font and allow table cells to wrap every time I create a report. It seems like this should be the default or at least a user should be able to set default settings for the...

What is the challenge? Moving from a different KB source into Aha! Knowledge requires manual copying, pasting, and reformatting. How would you solve it? An import tool that accepts HTML or JSON would speed up this process. What impact would it mak...

When preparing a presentation, if you accidentally delete a slide, there is no way to restore it. It would be great to have a recycle bin concept for deleted slides in a presentation that could allow you to restore a deleted slide. You could also ...

It would be helpful to have an option to configure roll up for delivery risks. For example, if a feature is at risk, we can reasonably assume the parent epic is also at risk, so we should display the flag there as well- with a link to the relevant...

Today the integration for this feature is not complete. It's not possible to search every document available in G Drive. It should be like this :

The product value score terminology works well for workspaces where teams are building products. But in other workspaces it can be confusing. In these cases a more generic field name would be easier to understand.