Integrity checker detects duplicate permissions on fresh JIRA installation/restoration

XMLWordPrintable

    • 6.03
    • 41
    • Severity 3 - Minor
    • 2
    • Hide
      Dear customers,

      The issue was resolved by extending the comparison of the permissions. Now it is being validated as in the following document: https://confluence.atlassian.com/adminjiraserver/using-the-database-integrity-checker-938847667.html#Usingthedatabaseintegritychecker-fixes-descriptionOverviewoftheintegritychecks
      under the check "Check the permissions aren't duplicated".

      Kind regards,
      Agata Kowal Software Engineer Jira DC
      Show
      Dear customers, The issue was resolved by extending the comparison of the permissions. Now it is being validated as in the following document: https://confluence.atlassian.com/adminjiraserver/using-the-database-integrity-checker-938847667.html#Usingthedatabaseintegritychecker-fixes-descriptionOverviewoftheintegritychecks under the check "Check the permissions aren't duplicated". Kind regards, Agata Kowal Software Engineer Jira DC

      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
          102 kB
          Daniel Leng

            Assignee:
            Agata Kowal
            Reporter:
            Daniel Leng (Inactive)
            Votes:
            60 Vote for this issue
            Watchers:
            73 Start watching this issue

              Created:
              Updated:
              Resolved: