Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-4922

Allow JSD to make comment required on transition in Customer Portal

    • 723
    • 3
    • 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

      Currently in JSD, if a workflow transition can be triggered on Customer Portal, a popup asking for an optional comment is displayed when customer triggers that transition.
      However there is no option in JSD/Workflow settings that can make this comment field mandatory.

      Suggested Solution

      Add an option in JSD or Workflow settings that allows administrator to make this comment field mandatory.

          Form Name

            [JSDCLOUD-4922] Allow JSD to make comment required on transition in Customer Portal

            We would really appreciate this feature so Approvers can comment on why they do not approve a request.

            Hans.Maarten.Vink added a comment - We would really appreciate this feature so Approvers can comment on why they do not approve a request.

            We really need this for escalations!

            Judy Forrister added a comment - We really need this for escalations!

            not just add an option in JSD or Workflow settings that allows administrator to make this comment field mandatory, while performing a webhook to another platform (eg ServiceNOW), the field is using a different payload and the comments will not be reflected in ServiceNOW.

            This results in agents in the other platform unable to view the comments and reason the status was transited.

            Thus would appreciate this feature can be fixed as well.

            Zhi-Xian Goh added a comment - not just add an option in JSD or Workflow settings that allows administrator to make this comment field mandatory, while performing a webhook to another platform (eg ServiceNOW), the field is using a different payload and the comments will not be reflected in ServiceNOW. This results in agents in the other platform unable to view the comments and reason the status was transited. Thus would appreciate this feature can be fixed as well.

            Happy New Year, everyone! May it be filled with joy, success, and - who knows - maybe even some miracles. Like Atlassian resolving to fix this bug. We can dream, right?

            Tobias Bosshard added a comment - Happy New Year, everyone! May it be filled with joy, success, and - who knows - maybe even some miracles. Like Atlassian resolving to fix this bug. We can dream, right?

            +1

            Anna Burger added a comment - +1

            +1

            Marco Feil added a comment - +1

            +1

            +1

            Please add this feature.

            Thanks in advance!

            Gus Sanchez added a comment - +1 Please add this feature. Thanks in advance!

            +1

            Leonel Goitia added a comment - +1

            +1

            Markus Zeiler added a comment - +1

              d0d1ba410583 Sushant Koshy
              cmao Chen Mao (Inactive)
              Votes:
              442 Vote for this issue
              Watchers:
              217 Start watching this issue

                Created:
                Updated: