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

Inequality JQL clauses require permission on the issue specified in the clause

    XMLWordPrintable

Details

    • 6.03
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 28 May 2018

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 28 May 2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

    Description

      Let's assume there is an issue called ABC-4 (ID: 10015) that user Fred doesn't have permission to see.

      State of things before https://jira.atlassian.com/browse/JRA-36368:
      If Fred tried issue ID 10015 in any of JQL clauses like:
      issue != 10015
      issue in (10014, 10015)
      issue not in (10014, 10015)
      issue > 10015
      issue >= 10015
      issue < 10015
      issue <= 10015
      he used to get an error and the query wouldn't run.

      After fixes for JRA-36368, we no longer load each issue individually to make sure they exist. As a side effect the permission check on the clause is gone. The permission filter is applied when the query runs.

      Now, as long as issues exist they can participate in JQL clauses. As a result, these queries return what user expects:
      issue != 10015: returns other issues, even though the user can't see this particular one
      issue in (10014, 10015): returns only 10014
      issue not in (10014, 10015): returns everything else, except these two issues

      BUT, these queries still don't return anything:
      issue > 10015
      issue >= 10015
      issue < 10015
      issue <= 10015

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              kshekhar Kiran (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: