Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-8662

Assign a story to future sprint

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • None
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      As Patrick I want to be able to assign a story to a future sprint so that it's query-able (via sprint id).

      A/C:

      1. I am able to create future sprints which I can assign issues to
      2. I'm able to remove future sprints and the issues are removed from them
      3. I'm able to move issues between future sprints and out of future sprints and the db is updated accordingly
      4. The backlog shows all future sprints, regardless of whether they are empty or not

      Notes:

      • as part of this, the necessary DB work to enable future sprints needs to happen

      Dev Notes

      Functionality that changes:

      • Send to Top (from JIRA)
      • Sprint dragging will not include filtered issues

      Q: What happens if a sprint becomes orphaned aka all assigned boards are deleted?
      A: Not Answered

      Q: What if the sprint's owning board was deleted but it was visible on a second board?
      A: Not Answered

      Q: What if a non-visible orphaned sprint was included in the filter of a new board? Is it reassigned?
      A: Not Answered

      Q: What if there are multiple rank fields?
      A: Not Answered

      Q: Do sprints need their own rank field? If so, is it locked? What if it is deleted/modified in JIRA 5.1?
      A: Not Answered

      Q: What are the conditions for the migration task?
      A: Not Answered

      Q: What happens to sprints for which all issues have been deleted?
      A: Not Answered

      Q: What if an issue is assigned to more than 1 future sprint via different boards?
      A: Not Answered

        1. Screen shot 2013-06-05 at 11.04.59 AM.png
          Screen shot 2013-06-05 at 11.04.59 AM.png
          23 kB
        2. Screen shot 2013-06-04 at 5.52.41 PM.png
          Screen shot 2013-06-04 at 5.52.41 PM.png
          38 kB
        1.
        		 Look at Remove from Sprint behaviour Sub-task Closed Unassigned
        2.
        		 Fix up Plan Drag and Drop Sub-task Closed Unassigned
        3.
        		 Visibility of sprint issues not updated upon instant filtering Sub-task Closed Unassigned
        4.
        		 Editing of Sprint name,start and end date Sub-task Closed Unassigned
        5.
        		 Test all ranking stuff Sub-task Closed Unassigned
        6.
        		 Check Report mode Sprint Selection Sub-task Closed Unassigned
        7.
        		 Sprints displayed on issue page agile panel Sub-task Closed Unassigned
        8.
        		 Fix up j/k behaviour Sub-task Closed Unassigned
        9.
        		 Warn when removing issues from an active sprint Sub-task Closed Unassigned
        10.
        		 DnD on an expanded active sprint with no issues doesn't work Sub-task Closed Unassigned
        11.
        		 empty active sprint message is wrong Sub-task Closed Unassigned
        12.
        		 Empty sprint progress badges have no height Sub-task Closed Unassigned
        13.
        		 UpgradeTask to set started flag of all sprints Sub-task Closed Unassigned
        14.
        		 Fix up tests Sub-task Closed Unassigned
        15.
        		 Show confirmation message when adding an issue to an active sprint Sub-task Closed Unassigned
        16.
        		 JS error when dragging sprint dragger Sub-task Closed Unassigned
        17.
        		 Wrong empty state text color Sub-task Closed Unassigned
        18.
        		 Cannot select issues in multiple sprints now Sub-task Closed Unassigned
        19.
        		 Cannot remove flag from issues that span multiple sprints Sub-task Closed Unassigned
        20.
        		 User without the schedule permission gets the wrong error message when trying to rank. Sub-task Closed Unassigned
        21.
        		 A sprint which was emptied cannot be queried in Report mode and generates error message Sub-task Closed Unassigned
        22.
        		 If there are no active or future sprints, the sprint name is always Sprint 1 Sub-task Closed Unassigned
        23.
        		 Deleting an empty future sprint causes an error Sub-task Closed Unassigned
        24.
        		 Burndown chart attempts to load future sprint Sub-task Closed Unassigned
        25.
        		 Sprint burndown gadget does not show a list of sprints Sub-task Closed Unassigned

            npetrov Nikolay Petrov (Inactive)
            tkotecki Tom Kotecki (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: