-
Suggestion
-
Resolution: Obsolete
-
None
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Currently for JIRA Service Desk, users are able to configure whether to enable the pre-populated commenting in the user profile as per the release at 18th October.
Customer would like to have this included on User Default Settings like autowatch and others so that it could be configured to trigger instance wide.
- is superseded by
-
JSDSERVER-3922 Service Desk pre-populated comments are missing
-
- Closed
-
- relates to
-
- Closed
[JSDSERVER-2506] Allow Pre-populated Commenting to be Configured Instance Wide
Cian Leahy
added a comment - The motivation for this is simple.
As an organisation, we do not have external customer access and use the Jira suite primarily as a software development tool. Service Desk is used basically as a portal to ensure that users are cleanly opening the right types of issues and filling in minimal fields to keep it as a clean as possible.
Having pre-populated templates for every single comment in Jira wastes time for every user who comments on a bug, feature or task. It also doesn't make sense - people expect to comment for the group working or watching the tickets. It isn't a 1-1 conversation.
Worse again, it pollutes the individual tickets making them unreadable with all this unnecessary space and fluff.
This "feature" in Service Desk completely degrades the Jira Software experience. I can't understand how this filtered through the requirements process for Jira Software when splitting off the two products
Yes, users can now individually disable this, but this absolutely should be an administrator function. The reality is that everyone will not disable out of inertia and administrators will have to waste hours/days/weeks tracking down users to get them to implement the change.
Cian Leahy
added a comment - The motivation for this is simple.
As an organisation, we do not have external customer access and use the Jira suite primarily as a software development tool. Service Desk is used basically as a portal to ensure that users are cleanly opening the right types of issues and filling in minimal fields to keep it as a clean as possible.
Having pre-populated templates for every single comment in Jira wastes time for every user who comments on a bug, feature or task. It also doesn't make sense - people expect to comment for the group working or watching the tickets. It isn't a 1-1 conversation.
Worse again, it pollutes the individual tickets making them unreadable with all this unnecessary space and fluff.
This "feature" in Service Desk completely degrades the Jira Software experience. I can't understand how this filtered through the requirements process for Jira Software when splitting off the two products
Yes, users can now individually disable this, but this absolutely should be an administrator function . The reality is that everyone will not disable out of inertia and administrators will have to waste hours/days/weeks tracking down users to get them to implement the change.
Hello,
Due to popular demand for functionality to turn off the pre-populate commenting feature and the low usage we experience with this feature we have decided to remove this feature from JIRA Service Desk. Please refer to
JSD-3922for additional details.Cheers!
Tim | Atlassian