Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-24969

Disabled user still counts towards license limit

XMLWordPrintable

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

      A disabled user which is a memeber of a group which has 'Use Confluence' permissions is still counted towards the license limit.

      The expected behaviour is that a disabled user does not count towards the license limit, regardless of what groups that disabled user might have been a member of. It would be understandable if re-enabling such a user might return an error if that user would then breach the licensed limit.

      We worked around the issue by removing all disabled users from all groups, but that's effectively historical data loss (in addition to being unintuitive).

            [CONFSERVER-24969] Disabled user still counts towards license limit

            Adam Barnes (Inactive) added a comment -

            This ticket is being resolved as we have never been able to reproduce the issue and have not had any new reports in nearly 2 years. If you are still experiencing this issue in a supported version and can provide steps to reproduce then please let us know.

            Adam Barnes (Inactive) added a comment - This ticket is being resolved as we have never been able to reproduce the issue and have not had any new reports in nearly 2 years. If you are still experiencing this issue in a supported version and can provide steps to reproduce then please let us know.

            Denise Unterwurzacher [Atlassian] (Inactive) added a comment -

            Hi kyle.varga. This issue does not happen 'out of the box', so we have not been able to reproduce it. There must be something additional factor in your instance that is causing it. I'd recommend getting in touch with Support - they can help you fix it up, or help us identify the additional factor that is causing it, so we can resolve it.

            Denise Unterwurzacher [Atlassian] (Inactive) added a comment - Hi kyle.varga . This issue does not happen 'out of the box', so we have not been able to reproduce it. There must be something additional factor in your instance that is causing it. I'd recommend getting in touch with Support - they can help you fix it up, or help us identify the additional factor that is causing it, so we can resolve it.

            Kyle Varga added a comment -

            Any update here?

            Kyle Varga added a comment - Any update here?

            JG Meillaud added a comment -

            Hello,

            I'm experiencing the same bug.

            I think this is a major bug.

            Cheers,
            JG

            JG Meillaud added a comment - Hello, I'm experiencing the same bug. I think this is a major bug. Cheers, JG

            Kai Sun added a comment -

            Will Atlassian fix this?

            Kai Sun added a comment - Will Atlassian fix this?

            Anatoli added a comment -

            Thanks for reporting this issue David.

            Anatoli added a comment - Thanks for reporting this issue David.

              Unassigned Unassigned
              ba81b6334429 David Harris
              Affected customers:
              17 This affects my team
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: