Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-41886

Integrity checker detects duplicate permissions on fresh JIRA installation/restoration

XMLWordPrintable

      The "Check for Duplicate Permissions" option in the Integrity Checker shows 4 duplicates, even on a fresh installation: DupePerms.jpg

      Checking in the database:

      SELECT * FROM schemepermissions WHERE ID IN (10003, 10032, 10100, 10101);

      We get:

      10003		24	group	jira-developers	
10032		22	group	jira-users	
10100		33	group	jira-users	
10101		44	group	jira-administrators

      Clicking on the "Fix" will proceed to delete all the entries above.

      Search for the System Administration global permission group entry:

      select * from schemepermissions where PERMISSION=44;

      We received an empty results which mean the JIRA System Administrators global permission group got deleted.

      There are no perceived side effects if I log-in using the JIRA System Administrators user account.

      Additional Notes
      I think it is also worth explaining on why the Integrity Checker manages to find these as "duplicates", when there isn't actually any duplication in the first place. There is only one instance of 22, 24, 33 and 44 permissions in a fresh installation, so there isn't any "duplicates". Also, why does removing them show no side effects even though permission 44 is actually the JIRA System Administrators global permission ?

        1. DupePerms.jpg
          DupePerms.jpg
          102 kB

          Form Name

            [JRASERVER-41886] Integrity checker detects duplicate permissions on fresh JIRA installation/restoration

            JM R. added a comment -

            They will never fix this.

            In any case it would be broken again in the next release.

            The best way forward would be to remove the stuff that is not working anyway

            JM R. added a comment - They will never fix this. In any case it would be broken again in the next release. The best way forward would be to remove the stuff that is not working anyway

            Bipin Nepal added a comment -

            Still seen in 8.22.6, fix this ASAP

            Bipin Nepal added a comment - Still seen in 8.22.6, fix this ASAP

            Brett Connor added a comment - - edited

            Appeared recently on 8.5.1 stable instance. Appears also to trip up some plugins.

            Brett Connor added a comment - - edited Appeared recently on 8.5.1 stable instance. Appears also to trip up some plugins.

            Raffael.eiler added a comment -

            Still seen in 8.15

            Raffael.eiler added a comment - Still seen in 8.15

            Bill Wohler added a comment -

            Still seen on a fresh 8.13 install!

            Bill Wohler added a comment - Still seen on a fresh 8.13 install!

            Joshua Sisk added a comment -

            Seen on an 7.11 install that was fresh, not upgraded from a previous install.

            Joshua Sisk added a comment - Seen on an 7.11 install that was fresh, not upgraded from a previous install.

            JIRA Admins added a comment -

            this seen after upgrading 7.0.11 to 7.7.2

            JIRA Admins added a comment - this seen after upgrading 7.0.11 to 7.7.2

            william@perasotech.com added a comment -

            Seen this after upgrade from 7.1.8  to 7.2.4 

            william@perasotech.com added a comment - Seen this after upgrade from 7.1.8  to 7.2.4 

            MattS added a comment - - edited

            This really should not happen on a newly installed instance. It looks like leftover false positive errors from the change to JIRA 7.x.

            Once the error has been fixed by the Integrity Checker, does it ever reappear?

            If it's not going to get fixed, please can we have a KB article on it?

            MattS added a comment - - edited This really should not happen on a newly installed instance. It looks like leftover false positive errors from the change to JIRA 7.x. Once the error has been fixed by the Integrity Checker, does it ever reappear? If it's not going to get fixed, please can we have a KB article on it?

            Sanjay Krishnan added a comment -

            We faced the same while upgrading from 6.2.7 to 6.4.14

            As there were no grounds for this error, we ignored the warning.

            But it's still irritating and time consuming for double checking this hoax warning.

            Sanjay Krishnan added a comment - We faced the same while upgrading from 6.2.7 to 6.4.14 As there were no grounds for this error, we ignored the warning. But it's still irritating and time consuming for double checking this hoax warning.

              e2656c68d96d Agata Kowal
              dleng Daniel Leng (Inactive)
              Affected customers:
              60 This affects my team
              Watchers:
              73 Start watching this issue

                Created:
                Updated:
                Resolved: