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

Shared filter queries break when users don't have browse permissions for projects in the search query

XMLWordPrintable

      Steps to replicate:

      • Create a shared filter having similar JQL: 
        project in (PROJECT1, PROJECT2) ORDER BY created DESC
      • Execute the shared filter with a user that does not have browse permissions for project PROJECT1
      • The resulting JQL becomes: 
        project in (10020, PROJECT2)
      • The non-viewable projects ID is replaced with numeric ID, and the sort order is missing
      • The filter initially displays the results with default sorting (Key descending) from under the View tab (even though the JQL summary is wrong), but once switching to Edit no results return with the displayed error message:
        "A value with ID '10020' does not exist for the field 'project'."
      • The user is unable to switch back to simple mode to edit the shared filter

            [JRASERVER-20578] Shared filter queries break when users don't have browse permissions for projects in the search query

            Veenu Bharara (Inactive) added a comment -

            Verified with QA Bamboo build 411-9, the issue is fixed, hence marking it resolved.

            Veenu Bharara (Inactive) added a comment - Verified with QA Bamboo build 411-9, the issue is fixed, hence marking it resolved.

            Michael Tokar added a comment -

            Fix has now been committed on temporary bug fix branch. Note that the fix only involved preserving the ORDER BY clause of search requests.

            Michael Tokar added a comment - Fix has now been committed on temporary bug fix branch. Note that the fix only involved preserving the ORDER BY clause of search requests.

            Oswaldo Hernandez (Inactive) added a comment -

            Committed to trunk. Must commit to 4.1.x branch before resolving.

            Oswaldo Hernandez (Inactive) added a comment - Committed to trunk. Must commit to 4.1.x branch before resolving.

            Jamie Echlin added a comment -

            This was reported based on https://support.atlassian.com/browse/JSP-53457.

            > I have replicated the bug in 4.0.1 and 4.0.2. It seems the filter works when executed from the Issues menu (regardless of the numerical project ID in the JQL summary on the View tab).

            I don't see this behaviour, it doesn't work for me on the View tab. Well, issues are returned and the set of issues is correct, but the sort is wrong. The sort being broken is the key thing in this bug, as far as I'm concerned.

            Jamie Echlin added a comment - This was reported based on https://support.atlassian.com/browse/JSP-53457 . > I have replicated the bug in 4.0.1 and 4.0.2. It seems the filter works when executed from the Issues menu (regardless of the numerical project ID in the JQL summary on the View tab). I don't see this behaviour, it doesn't work for me on the View tab. Well, issues are returned and the set of issues is correct, but the sort is wrong. The sort being broken is the key thing in this bug, as far as I'm concerned.

              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              rguler Rahmani Guler [Atlassian]
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: