Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-15

Allow dependent Stories to be in same Sprint

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Fixed
    • 1.6.2
    • None
    • None

    • JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

    Description

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

      If I have a Story that is dependent on another, JIRA Portfolio will not put them in the same Sprint. I think it should, so long as the combined estimate for both does not exceed the Sprint length.

      Attachments

        1. constraint-off.png
          constraint-off.png
          131 kB
        2. constraint-on.png
          constraint-on.png
          137 kB

        Issue Links

          has a derivative of

          Suggestion - JPOSERVER-1617 Improve scheduling granularity

          • Gathering Interest
          is related to

          Suggestion - JPOSERVER-373 Stories with dependencies can still be scheduled to start at the same time

          • Closed
          relates to

          Suggestion - JSWCLOUD-20291 Allow dependent Stories to be in same Sprint

          • Closed

          Activity

            People

              Unassigned Unassigned
              ac6e38faf9dc Russell Smith
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

              Dates

                Created:
                Updated:
                Resolved:
                Archived: