Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-78958

Specifying the key of an issue that has a security level applied in the filter query might break the results

XMLWordPrintable

      Issue Summary

      If you specify the key of an issue that has a security level applied to it on the query of a filter used in gadgets, users that do not have the necessary permissions to access that issue will get an error when accessing the gadget's results.

      Steps to Reproduce

      • Create a filter that specify keys of issues (one of which has a security level applied)
        • E.g. project = Kanbanna AND issuetype = Story OR key in (KAN-27, KAN-33)
        • In that case the issue KAN-27 has a security level applied
      • Apply that filter on a pie chart gadget, and use the Status as the gadget's metric
      • Log in as an user that does not have permissions to view the issue KAN-27, and click on the results that include KAN-27:

      Expected Results

      When the user click on those results, the search will load correctly and will return the issues that the user has access to. Specially because the count next to the status name actually reflects the number of issues that the user has access to in that context:

      • For example, in the screenshot of that gadget, a user that has access to all issues that are in the In progress status will see 3 as the total count

      Actual Results

      When clicking on the results, the user will be taken to the issue search navigation, but the key of the issue that they don't have access to will be converted to the issue's ID instead, breaking the query:

      Issue does not exist or you do not have permission to see it.
      

      Workaround

      Make sure that the user has access to all issues in the results, or instruct them to remove the issue ID from the query to load the results correctly.

              Unassigned Unassigned
              lalmeida@atlassian.com Leonardo De Almeida
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: