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

As a user, I would like to be able to use JQL to retrieve all the issues in a specific sprint (open, current and closed)

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • Standalone
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Currently, the only way to retrieve issues that are in a sprint is to do what is suggested here: https://answers.atlassian.com/questions/85039/how-to-filter-by-sprint-now-we-re-using-rapid-boards/85043

      So, if you wanted to write your own filter to get back all the issues in a specific sprint, you have to know what all the issues in the sprint are!

      The only other way to currently filter is using the following JQL:

      Sprint in openSprints()
      or
      Sprint in closedSprints()
      

      The limitation being that if you have multiple open Sprints, you can't just get back the issues for one of them. If you've closed more than 1 sprint ever, you can't get back the contents of that specific sprint. And if you're planning a sprint, you can't get back anything.

      As we Fix Versions in and the 'Classic' way of doing things, where you can use JQL like:

      fixVersion = 'Sprint n'
      

      I'd like to be able to do the same with the Sprint field. E.g.

      Sprint = 'Sprint n'
      

      Filters are an essential part of how Jira works (especially when used with Dashboards). I'd love to be able to keep using them instead of only relying on the 'Agile' view to get any kind of window into projects managed by GreenHopper.

              Unassigned Unassigned
              2cf4168f866b Dan Burzynski
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: