Application

What is the challenge? The ability to create dependency maps for linked records is great, however this feature is not available for Initiatives. Our leaders would like to see the dependency maps at a higher level for the initiatives they own, and ...

What is the challenge? In the fixed workflows for approvals, the approval is generated when the item enters that status. This is unnecesarily confusing and doesn't allow the user to indicate when a record is ready for that approval, unless you cre...

Based on trends we have seen with idea submission, there is generally a few buckets submissions fall into that require an Admin Response. As such, we have drafted positioning templates to expedite a proper response in these situations. It would be...

To not save report changes requires three clicks: Click 'Views' Click 'Save Views' Click the last saved report. If I make a change to a report that I don't like, I would like an easy, one click to abandon my changes. It would also be more intuitive.

While it is possible to selectively expand lines as needed within Account > Workspaces, it would be helpful to have the ability to expand all lines with a single action. It can be easy to accidentally miss expanding a line and keep the workspac...

We have an Epic (Initiative) - Feature - Requirement breakdown structure. It would be very useful to be able to visualize the dependencies using these existing relations instead of requiring to add separate link specifically for the dependancy map.

The Idea detail via includes my list of To Dos for that idea I am working on. When I add the Idea Detail to a notebook it does not publish the to do list. My idea is to allow for to dos to be added to a not book by feature, release or idea.

When using requirements for estimations as an input to roadmap planning, it would be helpful to be able to add a standard set of requirements to the feature, for example where each requirement might identify a different resource type for estimatio...

Why were common editor buttons hidden under drop-downs ??? This is an unnecessary change and it's very inconvenient when working on features and requirements.

What is the challenge? Updates and notifications to the Knowledge Base rely on a user being logged in to the Knowledge Base itself to see these. What is the impact? Updates won't be shared in the way I want them to be. Describe your idea Users are...