• 1,124
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      Problem Definition

      The default tab for the Comment field is set to Reply to customer during the transitions, whereby users may accidentally write a comment that a customer should not see.
      On the issue view, the default is Add internal note where agents may add comments that should be to the customers, but it ends up being internal and customers will never be notified.

      Suggested Solution

      Allow user to choose default tab for Comment field.

      <ul id="sd-comment-tabs" class="tabs horizontal">
      	<li class="js-sd-external-comment active ">
      		<a>Respond to customer</a>
      	</li>
      	<li class="js-sd-internal-comment inactive">
      		<a>Internal comment</a>
      	</li>
      </ul>
      

          Form Name

            [JSDCLOUD-1928] Allow admin to configure default tab for Comment field

            Our cases are all internal facing, so Internal Note is hardly used. I really don't understand that Atlassian implemented a change with this impact with giving Administrators the option to select a default of their own choice. Yet another reason to start using ServiceNow.

            Christophe Veuskens added a comment - Our cases are all internal facing, so Internal Note is hardly used. I really don't understand that Atlassian implemented a change with this impact with giving Administrators the option to select a default of their own choice. Yet another reason to start using ServiceNow.

            Many of our users are used to using "Reply to customer," as that's the only option we normally use. We very rarely use internal comments. Now we're experiencing that several messages to customers have been missed because users can’t choose their preferred setting themselves.

            Rasmus Fuursted added a comment - Many of our users are used to using "Reply to customer," as that's the only option we normally use. We very rarely use internal comments. Now we're experiencing that several messages to customers have been missed because users can’t choose their preferred setting themselves.

            We should have the ability to decide whether to retain the current settings. While we prefer the "Reply to Customer" option, we cannot be compelled to adopt a predefined approach based solely on your perspective.

            The curent default setting often leads to confusion, as customers frequently remain unaware of the actions taken within their tickets.

            Allow our administrators the flexibility to choose between an internal note or a customer reply as the default option. Please do not impose a rigid strategy upon us

             

            -Siva R

            Siva Ramasamy added a comment - We should have the ability to decide whether to retain the current settings. While we prefer the "Reply to Customer" option, we cannot be compelled to adopt a predefined approach based solely on your perspective. The curent default setting often leads to confusion, as customers frequently remain unaware of the actions taken within their tickets. Allow our administrators the flexibility to choose between an internal note or a customer reply as the default option. Please do not impose a rigid strategy upon us   -Siva R

            I believe that BOTH locations should be configurable. When our transition window pops up when moving a ticket to In Progress, it should default to Reply to Customer so that we can immediately let our customer know that we are working on their ticket. We require a response to the customer within a few hours.

            We don't mind the main comments entry field defaulting to Internal, as we are used to clicking Reply to Customer when we're ready to provide more information.

            As others have said, this should be configurable by administrators.

            Edward McPike Jr added a comment - I believe that BOTH locations should be configurable. When our transition window pops up when moving a ticket to In Progress, it should default to Reply to Customer so that we can immediately let our customer know that we are working on their ticket. We require a response to the customer within a few hours. We don't mind the main comments entry field defaulting to Internal, as we are used to clicking Reply to Customer when we're ready to provide more information. As others have said, this should be configurable by administrators.

            I think it's beter to let the admin deside what's the best for the company, So I think the best solution is to an option that we can choice by ourself.

            Bart Van den Bossche added a comment - I think it's beter to let the admin deside what's the best for the company, So I think the best solution is to an option that we can choice by ourself.

            I 100% agree with others, that this change was going to make some happy and others very frustrated. 

            Atlassian, there needs to be an option. This cannot be hard if you're flipping the field between one or the other selection as a default, to add a property and allow site admins to change the default. 

            This has made our customers very irate and updated, understandably, as we, too, have people not noticing that the default changed and that comments are going internal now. 

            Ken Maglio - WWT added a comment - I 100% agree with others, that this change was going to make some happy and others very frustrated.  Atlassian, there needs to be an option. This cannot be hard if you're flipping the field between one or the other selection as a default, to add a property and allow site admins to change the default.  This has made our customers very irate and updated, understandably, as we, too, have people not noticing that the default changed and that comments are going internal now. 

            The change is honestly hideous. We've got staff left and right replying internally and not directly to the customer, and while we can try and force a change in habits it just doesn't flow for what we do. This is a service management product, when we resolve a ticket we want to communicate with the customer. This should have been an optional change, a simple toggle, yet you chose to listen to a specific subset of customers rather than polling all customers.

            Tyler Saddington added a comment - The change is honestly hideous. We've got staff left and right replying internally and not directly to the customer, and while we can try and force a change in habits it just doesn't flow for what we do. This is a service management product, when we resolve a ticket we want to communicate with the customer. This should have been an optional change, a simple toggle, yet you chose to listen to a specific subset of customers rather than polling all customers.

            Our customers are also missing out on comments as the "Internal" comment is default. Making a global change that's not configurable like this is making normal workflows for agents difficult. Please give us the ability to have an administrator configure which they'd like to use as a default.

            Danial Schaffer added a comment - Our customers are also missing out on comments as the "Internal" comment is default. Making a global change that's not configurable like this is making normal workflows for agents difficult. Please give us the ability to have an administrator configure which they'd like to use as a default.

            Norman added a comment -

            Make the internal/customer option adjustable per account or group as soon as possible. In addition, for future changes to core processes, please study the consequences first.

            Norman added a comment - Make the internal/customer option adjustable per account or group as soon as possible. In addition, for future changes to core processes, please study the consequences first.

            Julia H. added a comment -

            Due to the recent change that all comments on the resolution screen are now suddenly INTERNAL (without a message from Atlassian!), we have escalations because our customers don't get the resolution comments anymore as our agents are working "as usual" and now the default has changed to internal instead of reply to customer.
            Now we have to inform the whole company to be aware of this and change their behavior because of the fact that this is NOT CONFIGURABLE from admin side!! Big big

            Julia H. added a comment - Due to the recent change that all comments on the resolution screen are now suddenly INTERNAL (without a message from Atlassian!), we have escalations because our customers don't get the resolution comments anymore as our agents are working "as usual" and now the default has changed to internal instead of reply to customer. Now we have to inform the whole company to be aware of this and change their behavior because of the fact that this is NOT CONFIGURABLE from admin side!! Big big

              Unassigned Unassigned
              cchan Chung Park Chan
              Votes:
              242 Vote for this issue
              Watchers:
              132 Start watching this issue

                Created:
                Updated: