Uploaded image for project: 'Confluence Server'
  1. Confluence Server
  2. CONFSERVER-22349

Remove unnecessary ContentPermissionSet object and database table

    XMLWordPrintable

    Details

    • Feedback Policy:
      We collect Confluence 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.

      Description

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      There really is no good reason to have content permission sets in Confluence. Content should related directly to ContentPermission. This will simplify our permission checking, and would have gone some of the way in preventing weird bugs like CONF-19914. I've spoken to Charles about this already - in fact he brought up the idea before I could even get to it.

      I originally planned to do this as part of CONF-22123 but didn't have enough time so I had to raise it as a separate task.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              nbhawnani Niraj Bhawnani
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: