• 936
    • 99
    • Hide
      Atlassian Update – 8 July 2020

      Hi everyone,

      Thank you for your votes and comments on this suggestion.

      We’re glad to announce that ability to restrict the sprints shown in the 'Sprint Field' will be available in the upcoming Jira 8.11.0 release.

      In short, we added an option in Jira Software configuration to filter sprint suggestions based on the project relevant for the given issue. This will be an opt-in, instance wide setting.

      For cases where no project is specified in the board's JQL, we will add a checkbox to display all sprint suggestions. A similar checkbox is now displayed in the Epic field. This will be useful for sprints on boards configured using labels or components only, for example.

      On the list with sprint suggestions we've also added board names for clarity.

      Thank you

      Grażyna Kaszkur
      Product Manager, Jira Server and Data Center

      Show
      Atlassian Update – 8 July 2020 Hi everyone, Thank you for your votes and comments on this suggestion. We’re glad to announce that ability to restrict the sprints shown in the 'Sprint Field' will be available in the upcoming Jira 8.11.0 release. In short, we added an option in Jira Software configuration to filter sprint suggestions based on the project relevant for the given issue. This will be an opt-in, instance wide setting. Now implemented via: Limiting sprint selection to relevant sprints For cases where no project is specified in the board's JQL, we will add a checkbox to display all sprint suggestions. A similar checkbox is now displayed in the Epic field. This will be useful for sprints on boards configured using labels or components only, for example. On the list with sprint suggestions we've also added board names for clarity. Thank you Grażyna Kaszkur Product Manager, Jira Server and Data Center
    • 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.

      Problem Definition

      Currently, there does not seem to be anything that limits which Sprint an issue can be added into when done via the Issue View Screen (with the 'Sprint' field). This can cause confusion as it could show Sprints from boards from a different project or cause users to link the issue to the wrong Sprint due to Sprints having the same name.

      Suggested Solution

      Have a feature where JIRA will warn users that the issue(s) is being added into a Sprint that was created in a Board from different a project - validate this with the Board JQL too.

      Workaround

      Since Sprint names are not unique in JIRA, try using unique Sprint names with a prefix of the Project so that it will be easier to distinguish them.

        1. Screen Shot 2015-07-17 at 18.24.43.png
          Screen Shot 2015-07-17 at 18.24.43.png
          99 kB
        2. Screen Shot 2015-07-17 at 18.25.06.png
          Screen Shot 2015-07-17 at 18.25.06.png
          41 kB
        3. Screen Shot 2015-07-21 at 08.52.34.png
          Screen Shot 2015-07-21 at 08.52.34.png
          72 kB
        4. sprint.png
          sprint.png
          27 kB
        5. sprints.png
          sprints.png
          37 kB

          Form Name

            [JSWSERVER-10805] Ability to restrict the sprints shown in the 'Sprint Field'

            if the user selects Show sprints from selected Project, "Recent" sprint list is still showing sprints from other projects. Should flag control both, Sprint list and Recent sprint list?

             

            Anita Chitragar added a comment - if the user selects Show sprints from selected Project, "Recent" sprint list is still showing sprints from other projects. Should flag control both, Sprint list and Recent sprint list?  

            +1

            lucas.giering added a comment - +1

            This story has been closed for 1.5 years!  Stop adding "+1 for cloud" comments here and go follow the linked issue, JSWCLOUD-10805.

            James Tuttle added a comment - This story has been closed for 1.5 years!  Stop adding "+1 for cloud" comments here and go follow the linked issue, JSWCLOUD-10805 .

            +1

            +1 for Jira Cloud

            Johnny Hermann added a comment - +1 for Jira Cloud

            Agreed, why is this not a cloud option??  All we can set is Parallel Sprints as well.

            Matthew Cook added a comment - Agreed, why is this not a cloud option??  All we can set is Parallel Sprints as well.

            Julien Rey added a comment -

            Julien Rey added a comment - Link to the official documentation about this new feature: https://confluence.atlassian.com/jirasoftwareserver/limiting-sprint-selection-to-relevant-sprints-1014679373.html

            Is there a possibility to implement this also when splitting an issue?

            It seems, there is still the old implementation.

            David Ranzmeir added a comment - Is there a possibility to implement this also when splitting an issue? It seems, there is still the old implementation.

            Jeanette added a comment - - edited

            why is this option NOT availible in cloud aswell? really need it!

            https://jira.atlassian.com/browse/JSWCLOUD-10805

            Jeanette added a comment - - edited why is this option NOT availible in cloud aswell? really need it! https://jira.atlassian.com/browse/JSWCLOUD-10805

            Is this not supported in Jira Cloud? The only setting I can find is Parallel Sprint.

            Tjerk Muller added a comment - Is this not supported in Jira Cloud? The only setting I can find is Parallel Sprint.

              5b2ccddb8927 Anna Przybycień
              jtye Joe Wai Tye (Inactive)
              Votes:
              599 Vote for this issue
              Watchers:
              346 Start watching this issue

                Created:
                Updated:
                Resolved: