Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-476

Automation for Jira - Add the functionality of publishing comments with restrict visibility for Project Roles

    • 0
    • 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.

      Currently, Automation for Jira can't publish comments in an issue if there is a Comment Visibility restriction.

      The following error is shown if we tried to setup this:

      Error adding comment to issue
      You are currently not a member of the project role: <ROLE_NAME>. (commentLevel)

      It would be great if Automation for Jira could add comments to issues following the restriction established.

      The only workaround is to change the Rule's actor and set a user that has access to that Project role.

            [AUTO-476] Automation for Jira - Add the functionality of publishing comments with restrict visibility for Project Roles

            I've had an issue that appears related to this: https://community.atlassian.com/t5/Jira-Service-Management/Internal-Notes-Restriction-Feature-No-Longer-Passes-comment/qaq-p/2905940?utm_campaign=&utm_content=post&utm_medium=email&utm_source=atlcomm#U2906853

            Would be great to see progress here, I'm having to verbally warn my project board users not to use the new "restrict visibility" feature in order to avoid breaking my automations.

            Michaela Nelson added a comment - I've had an issue that appears related to this: https://community.atlassian.com/t5/Jira-Service-Management/Internal-Notes-Restriction-Feature-No-Longer-Passes-comment/qaq-p/2905940?utm_campaign=&utm_content=post&utm_medium=email&utm_source=atlcomm#U2906853 Would be great to see progress here, I'm having to verbally warn my project board users not to use the new "restrict visibility" feature in order to avoid breaking my automations.

            If left at the defaults, using the comment on issue automation and selecting a visibility will always fail. Seems like an oversight. It wouldn't be a huge problem but it also doesn't seem to be possible to add the Automation for Jira user to the project in the role for which I'm seeking to restrict comment visibility to. Hopefully, a real workaround (not going to run the rule as a static user) can be provided. Thanks.

            Joshua Baker added a comment - If left at the defaults, using the comment on issue automation and selecting a visibility will always fail. Seems like an oversight. It wouldn't be a huge problem but it also doesn't seem to be possible to add the Automation for Jira user to the project in the role for which I'm seeking to restrict comment visibility to. Hopefully, a real workaround (not going to run the rule as a static user) can be provided. Thanks.

              Unassigned Unassigned
              976c02b75079 Celso J
              Votes:
              12 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: