Cordelle
My feedback
14 results found
-
3 votesCordelle
supported this idea
·
-
3 votesCordelle
supported this idea
·
-
3 votesCordelle
supported this idea
·
-
6 votesCordelle
supported this idea
·
An error occurred while saving the comment -
419 votes
An error occurred while saving the comment Cordelle
commented
Really optimistic about the new custom questions feature however allowing them to surface in the extension but not the web portal makes them unusable for our org because it results in an inconsistent data entry experience and data collection. Our org would like to ask users to specify the 'use case' and 'impact' as separate fields since they are consistently not included in the description.
Cordelle
supported this idea
·
-
1 voteCordelle
shared this idea
·
-
4 votes
An error occurred while saving the comment Cordelle
commented
We have 7 custom fields that are only relevant to half of our forums. It would be ideal if we could select the forums where the custom fields should be visible so it doesn't clutter up the side panel and custom field modal for product teams that do not use these fields.
Cordelle
supported this idea
·
-
2 votesCordelle
shared this idea
·
-
24 votes
An error occurred while saving the comment Cordelle
commented
The impact for us is manually having to refresh and republish the report weekly, but ideally daily. We want to scale up the use of User Voice in our org and require dashboards to do so, and this is a roadblock.
Cordelle
supported this idea
·
-
1 voteCordelle
shared this idea
·
-
2 votesCordelle
shared this idea
·
-
1 voteCordelle
shared this idea
·
-
60 votesCordelle
supported this idea
·
-
160 votesCordelle
supported this idea
·
Love the Status Template messages but it would be ideal to configure these per forum rather than UV instance. (Ability to select which forum(s) the template applies to).
Our use case: Our forums are 1:1 with our products. 50% of our products are managed in-house and have a different message than the other 50% of products which are managed by a Vendor. We prefer to use 1 public status for end-user consistency regardless of who manages the product, but it would be ideal to have separate Status Template messages depending on whether the product team is in-house or external.