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

JIRA doesn't respect Project Permission in Generating JQL

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 6.3.15, 9.4.2, 9.11.1
    • JQL
    • 6.03
    • 2
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 06 November 2019

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 06 November 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

      Steps to Reproduce:
      • Create 2 projects. Project A and Project B
      • Create a custom label field which is available to both Project A and B.
      • Let's have two users. User A with Browse project permission to Project A only and User B who has Browse Project permission to both Project A and B.
      • Create an issue in either one of the projects and fill up the custom label field.
      • Login as User A and go to the issue detail page.
      • Click the custom label field value and the user will be directed to the issue navigator.
      • It will show an error "A value with ID '10000' does not exist for the field 'project'.
      Expected Behaviour:
      • JIRA should generate a JQL which is aligned to the permission granted to the user currently logged in. It shouldn't include a project ID where the user has no permission with. When you login as User B who has permission on both projects. No error was noted.
      Actual Behaviour:
      • An error was thrown when User A clicks on the custom label field value.
      Workaround:
      • Remove the project ID shown on the error from the JQL.

        1. 3.png
          3.png
          34 kB
        2. 2.png
          2.png
          93 kB
        3. 1.png
          1.png
          109 kB

              Unassigned Unassigned
              acardino Anna Cardino (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: