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

Scheduling wrongly plan work for the first release even if released or in the past

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Medium Medium
    • None
    • None
    • Scheduling
    • None

      For Kanban team, the first available piece of work is assigned to the first list release even if it's far in the past. The next piece of work is then assigned to the next release matching today's date as expected.

      Releases in Portfolio only `disappear` when archived, so this even happens on versions marked as `Released`.

       

      To reproduce:

      • Create a kanban team
      • Create an issue with an estimate and no release assignment
      • Add a release started/released way back in the past (optionally mark it as released in JIRA)
      • Calculate

      The issue will be assigned to the past release wrongly. Switching the team to scrum shows the correct behavior.

        1. Program Status Breakdown.png
          Program Status Breakdown.png
          20 kB

            [JPOSERVER-1900] Scheduling wrongly plan work for the first release even if released or in the past

              Unassigned Unassigned
              tbarthelemy Thomas
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

                Created:
                Updated:
                Resolved:
                Archived: