• 2
    • 4
    • 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.

      Problem

      Currently, it's not possible to leave restricted comments for Approvers who do not have application access to Jira.

      Suggestion

      Allow comment visibility configuration for Portal

      Why is it important

      • Example use case

        When we send an issue to an Approver, often we need to write a private
        comment for her - for example, to give her additional information that
        might help her to make a decision about approving or rejecting the request.
        Sometimes this information may include technical details or sensitive data
        that cannot be shared to other person. Thus, this kind of comment should
        be visible to the Approver only, and not to the Request participants.
        Moreover, usually the Approver does not have a JIRA account so we cannot
        use the internal comments for that.

          Form Name

            [JSDSERVER-5506] Restricted comments for Approvers

            +1

            +1

            Jian Liang Low added a comment - +1

            AJohnston added a comment -

            Agreed. The ability to add any comments to the approval email would be useful! Needed in JSDCloud too!

            AJohnston added a comment - Agreed. The ability to add any comments to the approval email would be useful! Needed in JSDCloud too!

            I second Susan's comment entirely.  Since the main purpose of the approval step of a workflow is to interact with the Approver, not the Reporter or participants, it makes no sense that the Approver is the one person who does not receive any comment included in the transition.

            We have worked around this by disabling the native approval notifications and set up Automation for Jira to imitate the native notification email and behavior, but also including any comment added via our "send for approval" screen, with internal comments still being included in the email to the approver(s). Unfortunately, the downside of doing this is that even though the approvers can see the comment in the email, if the view the request in the portal the internal comment will not be visible to them, possibly adding confusion.

            Jordan Nimlos added a comment - I second Susan's comment entirely.  Since the main purpose of the approval step of a workflow is to interact with the Approver, not the Reporter or participants, it makes no sense that the Approver is the one person who does not receive any comment included in the transition. We have worked around this by disabling the native approval notifications and set up Automation for Jira to imitate the native notification email and behavior, but also including any comment added via our "send for approval" screen, with internal comments still being included in the email to the approver(s). Unfortunately, the downside of doing this is that even though the approvers can see the comment in the email, if the view the request in the portal the internal comment will not be visible to them, possibly adding confusion.

            We need this also for the described use case. In most cases an approval is nothing you can approve/decline without any further information and putting more information in the issue description is not applicaple.  In addition it makes no sense that the Approver should be the only person who will not receive any comment information when adding one during the transition.

            Susan Piatek added a comment - We need this also for the described use case. In most cases an approval is nothing you can approve/decline without any further information and putting more information in the issue description is not applicaple.  In addition it makes no sense that the Approver should be the only person who will not receive any comment information when adding one during the transition.

            We need this for cloud for exactly the same use case described above.

            Vicki Lea Tsang added a comment - We need this for cloud for exactly the same use case described above.

              Unassigned Unassigned
              michin Michelle Chin
              Votes:
              31 Vote for this issue
              Watchers:
              18 Start watching this issue

                Created:
                Updated: