Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-9815

JQL using futureSprints() is not respecting the filters

XMLWordPrintable

      Steps to Reproduce:

      • Have more than one project with a planned Sprint.
      • Have users that don't have permissions on all these projects.
      • Run the below JQL specifying the project to search:
      project = "Project X" and Sprint IN futureSprints()

      Actual Behavior:

      Instead of showing only the issues in the project that the user has permission to view, the following error appears:

      Expected Behaviour:

      If I specified the project to see, it's not supposed to bring me those errors. Or at least it was supposed to bring the the issues which I have permission to see.

        1. Screen Shot 2013-09-12 at 6.08.57 PM.png
          Screen Shot 2013-09-12 at 6.08.57 PM.png
          50 kB

            [JSWSERVER-9815] JQL using futureSprints() is not respecting the filters

            Ian Dick added a comment -

            This was fixed in Jira Agile (Greenhopper) version 6.3.6, as a result of changes made for this issue -> https://jira.atlassian.com/browse/GHS-8401. Before 6.3.6, future sprints were not being filtered in the same way that open and closed sprints were, which was resulting in error messages being shown that a user lacking certain permissions should not see. The fix was confirmed present in versions 6.3.6 and master of Jira Agile, and the error was confirmed present in 6.3.5. I will now close this issue.

            Ian Dick added a comment - This was fixed in Jira Agile (Greenhopper) version 6.3.6, as a result of changes made for this issue -> https://jira.atlassian.com/browse/GHS-8401 . Before 6.3.6, future sprints were not being filtered in the same way that open and closed sprints were, which was resulting in error messages being shown that a user lacking certain permissions should not see. The fix was confirmed present in versions 6.3.6 and master of Jira Agile, and the error was confirmed present in 6.3.5. I will now close this issue.

            Hazel Elgart added a comment -

            We updated to Agile 6.3.11 a few weeks ago and have not seen this problem reoccur.

            Hazel Elgart added a comment - We updated to Agile 6.3.11 a few weeks ago and have not seen this problem reoccur.

            Wolfram Lührig added a comment -

            We have the same problem! Jira Agile 6.3.1

            Wolfram Lührig added a comment - We have the same problem! Jira Agile 6.3.1

            Greg added a comment -

            I have this issue in v6.0.6

            Greg added a comment - I have this issue in v6.0.6

            Philip Page added a comment -

            Is this still broken?

            Philip Page added a comment - Is this still broken?

            francis added a comment -

            Same problem here - GH 6.3.2.2
            This problem has been escalated by users (who don't have access to all projects)
            When they query

            sprint in futureSprints(), they get the error message, making the function unusable.

            francis added a comment - Same problem here - GH 6.3.2.2 This problem has been escalated by users (who don't have access to all projects) When they query sprint in futureSprints(), they get the error message, making the function unusable.

            Michael Tokar added a comment -

            In which version are you seeing this bug?

            Michael Tokar added a comment - In which version are you seeing this bug?

            Kim Wall added a comment -

            Thank you for opening this. However, I'd say it's more than minor as it keeps all users but essentially admins from being able to use that query.

            Kim

            Kim Wall added a comment - Thank you for opening this. However, I'd say it's more than minor as it keeps all users but essentially admins from being able to use that query. Kim

              idick Ian Dick
              aquadrospetry Andre Quadros Petry (Inactive)
              Affected customers:
              14 This affects my team
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: