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

Remove Customer Portal Access entity from all permissions currently not implemented

XMLWordPrintable

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

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

      Currently, several permissions have been granted to the "Customer Portal Access" entity, despite the functionality to provide these permissions the customer user types not being in place yet.
      These permissions have been granted as placeholders for potential future feature releases.

      This means, that as soon as such a feature gets release, and the JIRA Admin of the JIRA environment upgrades Service Desk, the customers in that environment will automatically get that permission granted.
      This can pose a security issue if the JIRA Admin does not want customers to have these permissions.

      Please remove these placeholders to prevent the potential security issue from above to occur. Instead, we need to properly inform customers when new feature become available, and which steps they need to take in order to provide these features to their customer.

          Form Name

            [JSDSERVER-3421] Remove Customer Portal Access entity from all permissions currently not implemented

            Charlie Marriott added a comment -
            Atlassian Update – 1 March 2021

            Hi,

            Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

            Regards,

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 1 March 2021 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Jira Service Management, Server & Data Center

              Unassigned Unassigned
              mnassette MJ (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: