What is the challenge? Currently, there are log events for successful updates made from Jira when using the "Update Records" action What is the impact? Users have no way of knowing which records were successfully updated and what fields were chang...

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

In my scenario, there are times that a feature is in a given status, and as a result, I would want that feature to move to a different release. For example, If I abandon a feature, I want it removed from a release and put into a parking lot where ...

When creating a pivot report across a number of products the Vision components are not available from the object list. My use case is that I would like to consuct a review of the assembled vision components across a number of products within a pro...

What is the challenge? Currently individual Aha! Knowledge add-on users can't create and manage document collections What is the impact? Their ability to manage knowledge bases is impacted as it requires a Customization Admin to create and...

Integrate with fresh desk for ideas and bugs

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...

What is the challenge? Aha! user can update any idea in portal that they can view, but can only add attachments to ideas that they created. Portal user (or Aha! user) can update any proxy vote in portal that they can view (when portal settings all...

Hi, I had a look at the capacity report and I think it has good potential. In order to make it useable for us, we would need to be able to define the standard weekly capacity per assignee, as well as exceptions such as leave, holidays etc. Th...

The value of “Status changed to <status X>” for a feature workflow appears to perpetually contain the date of the first time that the status was changes to <status X> rather than the date of the most recent transition to <status X&g...