Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-1928

Allow admin to configure default tab for Comment field

    XMLWordPrintable

Details

    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

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

      Problem Definition

      The default tab for Comment field is set to Respond to customer, whereby users may accidentally write a comment that a customer should not see.

      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>

      Attachments

        Issue Links

          duplicates

          Suggestion - JSDSERVER-1733 Make Internal Comments the default comment type

          • Closed
          is duplicated by

          Suggestion - JSDSERVER-1469 Add ability to configure default response target

          • Closed

          Suggestion - JSDSERVER-1733 Make Internal Comments the default comment type

          • Closed
          relates to

          Suggestion - JSDSERVER-1733 Make Internal Comments the default comment type

          • Closed

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

          • Gathering Interest

          Activity

            People

              Unassigned Unassigned
              cchan Chung Park Chan
              Votes:
              4 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync