• Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 6.1.3
    • None
    • 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.

      We run a bunch of reports for the current milestone. However using the new rapid board, we can't retrieve the issues in a sprint without knowing the id of the sprint.

      It would be nice to be able to jql search for the name of the sprint instead.

      As a workaround is it possible via rest to look up the sprint id when all i know is the name?

            [JSWSERVER-4949] Ability to search for issues based on sprint name

            Thanks tkotecki, that is great news!

            Nicholas Muldoon added a comment - Thanks tkotecki , that is great news!

            MarkW added a comment -

            Awesome news Tom. We are actually upgrading to that version this weekend! Our users will love it!

            MarkW added a comment - Awesome news Tom. We are actually upgrading to that version this weekend! Our users will love it!

            Tom Kotecki (Inactive) added a comment - - edited

            Hi All,

            Querying active and complete sprints has been implemented in 6.1.3: https://confluence.atlassian.com/display/GH/GreenHopper+6.1.3+Release+Notes#GreenHopper6.1.3ReleaseNotes-SearchforSprintbyName

            Since there is a separate issue that specifically covers future sprints (GHS-5773), this story is now complete.

            If you're interested in querying future sprints, please follow GHS-5773 for further updates.

            Many thanks

            Tom Kotecki
            Product Manager, GreenHopper

            Tom Kotecki (Inactive) added a comment - - edited Hi All, Querying active and complete sprints has been implemented in 6.1.3: https://confluence.atlassian.com/display/GH/GreenHopper+6.1.3+Release+Notes#GreenHopper6.1.3ReleaseNotes-SearchforSprintbyName Since there is a separate issue that specifically covers future sprints ( GHS-5773 ), this story is now complete. If you're interested in querying future sprints, please follow GHS-5773 for further updates. Many thanks Tom Kotecki Product Manager, GreenHopper

            Hi jamieechlin,

            Loving the issueFunction for finding issues in a specific board and sprint. Any chance this can be extended to find issues in the current sprint, whatever that sprint happens to be called?

            issueFunction in inSprint("My Board", currentSprint())

            Thanks Jamie,
            Nick Muldoon

            Nicholas Muldoon added a comment - Hi jamieechlin , Loving the issueFunction for finding issues in a specific board and sprint. Any chance this can be extended to find issues in the current sprint, whatever that sprint happens to be called? issueFunction in inSprint("My Board", currentSprint()) Thanks Jamie, Nick Muldoon

            Victor Hall added a comment - - edited

            I'm trying to build some visibility linking search data back over to Confluence for business areas, and finding the magic number is very clunky. Using "magic numbers" is bad practice. It's a surprising lack of consistency in design when I can query 'project in ("Project Z5") but not 'sprint in ("Z5-Sprint 201401")' (or almost any other fields, like fixVersion, etc). It really feels like it should be built in, and not rely on script packages be installed.

            Big +1 to this issue for large values of 1.

            Victor Hall added a comment - - edited I'm trying to build some visibility linking search data back over to Confluence for business areas, and finding the magic number is very clunky. Using "magic numbers" is bad practice. It's a surprising lack of consistency in design when I can query 'project in ("Project Z5") but not 'sprint in ("Z5-Sprint 201401")' (or almost any other fields, like fixVersion, etc). It really feels like it should be built in, and not rely on script packages be installed. Big +1 to this issue for large values of 1.

            JamieA added a comment -

            You can query on unstarted, active or complete sprints using a JQL function provided by the script runner plugin. It also uses some javascript to add a "View in Issue Navigator" link to each sprint in the planning board.

            Example: issueFunction in inSprint("My board", "Sprint 1")

            Docs plus couple of known issues here.

            Give it a try, and give me any feedback on the wiki page or ask questions at answers.

            JamieA added a comment - You can query on unstarted, active or complete sprints using a JQL function provided by the script runner plugin. It also uses some javascript to add a "View in Issue Navigator" link to each sprint in the planning board. Example: issueFunction in inSprint("My board", "Sprint 1") Docs plus couple of known issues here . Give it a try, and give me any feedback on the wiki page or ask questions at answers .

            "LAME!" Is what people tell me I explain you have to use the sprint ID. This feature seems must a must have and yet its missing.

            Kevin Shine added a comment - "LAME!" Is what people tell me I explain you have to use the sprint ID. This feature seems must a must have and yet its missing.

            None of the approaches for finding the sprint Id above worked for me (6.1.1). I think the best approach is to open any issue in the sprint, then under the Agile panel you will see a link to the Active Sprint, if you mouse over that you will get the sprint Id, eg: .../jira/secure/GHGoToBoard.jspa?sprintId=5624

            Jamie Echlin added a comment - None of the approaches for finding the sprint Id above worked for me (6.1.1). I think the best approach is to open any issue in the sprint, then under the Agile panel you will see a link to the Active Sprint, if you mouse over that you will get the sprint Id, eg: .../jira/secure/GHGoToBoard.jspa?sprintId=5624

            MattS added a comment -

            I get why Sprints have a unique id, just as custom fields do. I just don't want to have to explain to new GH users about how to find that magic number or why they should care. They see a Sprint named "Foo" and they want to search on "Foo", which seems obvious. If there are two Sprints named "Foo" then the JQL should autocomplete and tell you the GH boards they come from.

            MattS added a comment - I get why Sprints have a unique id, just as custom fields do. I just don't want to have to explain to new GH users about how to find that magic number or why they should care. They see a Sprint named "Foo" and they want to search on "Foo", which seems obvious. If there are two Sprints named "Foo" then the JQL should autocomplete and tell you the GH boards they come from.

            Edwin Stol added a comment -

            How would you do that, considering that a Rapid Board can contain more then one project? Which key does the sprint get then?
            Considering the 'global' sprint; why don't you create a 'monster board' for these teams?

            Edwin Stol added a comment - How would you do that, considering that a Rapid Board can contain more then one project? Which key does the sprint get then? Considering the 'global' sprint; why don't you create a 'monster board' for these teams?

              Unassigned Unassigned
              bmccoy bmccoy
              Votes:
              150 Vote for this issue
              Watchers:
              102 Start watching this issue

                Created:
                Updated:
                Resolved: