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

openSprints() JQL returns error if no open sprints exist

XMLWordPrintable

      NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.

      Summary

      When a non administrator user attempts to display sprints using the openSprints() JQL, they display the error as per the attached screenshot.

      Environment

      • JIRA 5.2.10
      • OS X 10.7.5
      • PostgreSQL 9.1

      Steps to Reproduce

      1. Create a new sprint.
      2. Add issues to it.
      3. Delete those issues.
      4. Attempt to view the sprint using a user that does not have the Administrator Global Permission, for example: 
        project = JRA and Sprint in opensprints()

        This can be reproduced here with https://jira.atlassian.com/issues/?jql=project%20%3D%20JRA%20and%20Sprint%20in%20opensprints()

      Expected Results

      There is no error presented to the user.

      Actual Results

      The user will receive the error as per the attached screenshot and below:

      Sprint with id 104 does not exist or you do not have permission to view it.

      Notes

      Similar to GHS-7659.

        1. Screenie.png
          Screenie.png
          91 kB

            [JSWSERVER-8401] openSprints() JQL returns error if no open sprints exist

            Honeywell JIRA Admin added a comment -

            @David Currie

            We have the same issue with query Sprint IN futureSprints()

            Honeywell JIRA Admin added a comment - @David Currie We have the same issue with query Sprint IN futureSprints()

            Joe Wisnewski added a comment - - edited

            My users are also getting this error. It makes openSprints() useless to them, even if they first limit the query to projects for which they have permissions...

            I am running Jira OnDemand v v6.1-OD-09-WN

            Joe Wisnewski added a comment - - edited My users are also getting this error. It makes openSprints() useless to them, even if they first limit the query to projects for which they have permissions... I am running Jira OnDemand v v6.1-OD-09-WN

            Dave C added a comment - - edited

            pobara the problem is that the user is using openSprints() as opposed to directly querying the sprint, so they would not expect to see the error message. If you queried the sprint directly, I would expect it to appear, however in this example I'd expect the error to be suppressed.

            Edit: Sorry, I should've made this more clearer. I've updated the issue and included the screenshot that was supposed to be attached.

            Dave C added a comment - - edited pobara the problem is that the user is using openSprints() as opposed to directly querying the sprint, so they would not expect to see the error message. If you queried the sprint directly, I would expect it to appear, however in this example I'd expect the error to be suppressed. Edit: Sorry, I should've made this more clearer. I've updated the issue and included the screenshot that was supposed to be attached.

            Peter Obara added a comment -

            If all issues have been removed from the sprint, this is correct behavior as the sprint no longer exists. If non-admin users get the error because there are still issues in the sprint hidden from them, the error is still correct. Is the description here different from those scenarios?

            Peter Obara added a comment - If all issues have been removed from the sprint, this is correct behavior as the sprint no longer exists. If non-admin users get the error because there are still issues in the sprint hidden from them, the error is still correct. Is the description here different from those scenarios?

            Honeywell JIRA Admin added a comment -

            This is happening in 6.2 version as well.

            Honeywell JIRA Admin added a comment - This is happening in 6.2 version as well.

              mtokar Michael Tokar
              dcurrie@atlassian.com Dave C
              Affected customers:
              12 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: