Leftover permission causes "user not found exception" in Assets schema roles group permissions

XMLWordPrintable

    • 1
    • Severity 2 - Major

      Problem

      Leftover from a user in assets permissions cause "NotFoundInsightException: User not found!" exception

      The issue appears when editing the permissions meaning adding, or removing users while the unknown user(s) are present.

      Users already in the permission group are not affected.

      Instance Details

      Jira version 9.12.12

      Investigation Done

      When an unknown user is present in the Assets permission group, updating members fails with "NotFoundInsightException: User not found!"

      • Reproduced in 9.12.12 and 10.4.0

      Environment

      • Reproduced in 9.12.12 and 10.4.0

      Steps to Reproduce

      1. Create a user in Jira user management{}
      2. Give it permission under the assets object schema roles
      3. Delete the user in Jira user management
      4. A leftover "unknown" user is left in the schema roles

      Expected Results

      No leftovers of the deleted user should remain in the schema role group permissions

      Actual Results

      After deleting the user an Uknow entry remains triggering the "NotFoundInsightException: User not found!" error.

      Workaround

      Manually remove the Uknown(s) user from the schema role permissions

      Notes

      Please enhance the user deletion to include the Assets schema role group permissions, or alternatively issue a warning to administrators regarding users in schema roles before their deletion.

        1. screenshot-4.png
          screenshot-4.png
          440 kB
        2. screenshot-3.png
          screenshot-3.png
          444 kB
        3. screenshot-2.png
          screenshot-2.png
          158 kB
        4. screenshot-1.png
          screenshot-1.png
          425 kB

            Assignee:
            Benjamin Suess
            Reporter:
            Sergio Soto Lopez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: