Remove unnecessary ContentPermissionSet object and database table

XMLWordPrintable

      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.

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

              Created:
              Updated:
              Resolved: