Prevent users from seeing 'NO ACCESS TO REQUEST' label at Customer Portal of user's comments that were removed from Project's Users and Roles

XMLWordPrintable

    • 3
    • 1

      Atlassian Update - October 2023

      Hi Everyone,

      Thank you for previously raising this feature request and bringing it to our attention.

      Within our company roadmap and work capacity, we try to address or review each feature request but admit that not each one will be implemented. To continue the culture of being honest and open, we are closing this ticket to focus on our upcoming roadmap for all Jira Service Management Cloud users. You can visit Atlassian Cloud Roadmap to learn more about what was recently released and the upcoming roadmap.

      Thank you again for providing valuable feedback to our team!

      Akriti Gupta
      Jira Service Management Cloud team

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

      Summary

      When a user is removed from Project Settings > User and roles all his comments are labeled with the information NO ACCESS TO REQUEST at JIRA and Customer Portal.

      Steps to Reproduce

      1. As a Service Desk Agent, comment at a Service Desk Issue
      2. Remove the user from Service Desk Team at *Project Settings > User and Roles
      3. Go to the Customer Portal and the label NO ACCESS TO REQUEST will be added at the user's comment

      Expected Results

      1. Prevent this information be shown at Customer Portal for Customer Portal users

      Actual Results

      All users can see the NO ACCESS TO REQUEST label at Customer Portal

      Workaround

      Remove only the user's Application access at User Management session

            Assignee:
            Unassigned
            Reporter:
            Coutinho (Inactive)
            Votes:
            4 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: