We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-21210

Create sprint screen does not re-calculate working days when moving start date past the current end date

      Problem

      When creating a sprint, setting the start date past the end date will cause the calculation of working days remaining to state "This sprint contains 0 working days" instead of automatically re-calculating the number of working days.

      Environment

      Jira Software 8.21.0

      Steps to Reproduce

      1. Navigate to a Scrum board backlog
      2. Click Create Sprint
      3. For Duration, select 1, 2, or 3 weeks
      4. Change the start date to a date that is later than the currently selected end date
      5. The end date field will update correctly to reflect the new end date, but the working days calculation will state "This sprint contains 0 working days".

      Expected Results

      The working days value is correctly calculated when changing the start date to a value past the currently selected end date.

      Actual Results

      The end date value changes automatically, but the working days value is reported as '0'.

      Workaround

      Click the calendar icon next to the End Date box and manually select the end date, this action will recalculate the working days correctly.

      Notes

      The 0 working days messaging is only incorrect in the 'Create Sprint' screen, once you create the sprint, the duration of the sprint is represented correctly.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Software Data Center'
            1. Jira Software Data Center
            2. JSWSERVER-21210

            Create sprint screen does not re-calculate working days when moving start date past the current end date

              • Icon: Bug Bug
              • Resolution: Fixed
              • Icon: Low Low
              • 9.11.0
              • 8.20.1, 8.21.0
              • Sprint
              • None

                Problem

                When creating a sprint, setting the start date past the end date will cause the calculation of working days remaining to state "This sprint contains 0 working days" instead of automatically re-calculating the number of working days.

                Environment

                Jira Software 8.21.0

                Steps to Reproduce

                1. Navigate to a Scrum board backlog
                2. Click Create Sprint
                3. For Duration, select 1, 2, or 3 weeks
                4. Change the start date to a date that is later than the currently selected end date
                5. The end date field will update correctly to reflect the new end date, but the working days calculation will state "This sprint contains 0 working days".

                Expected Results

                The working days value is correctly calculated when changing the start date to a value past the currently selected end date.

                Actual Results

                The end date value changes automatically, but the working days value is reported as '0'.

                Workaround

                Click the calendar icon next to the End Date box and manually select the end date, this action will recalculate the working days correctly.

                Notes

                The 0 working days messaging is only incorrect in the 'Create Sprint' screen, once you create the sprint, the duration of the sprint is represented correctly.

                        65f46f08128b Mikołaj Pajor (Inactive)
                        bf5a24f1e03c Christopher Brown (Inactive)
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        0 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              65f46f08128b Mikołaj Pajor (Inactive)
                              bf5a24f1e03c Christopher Brown (Inactive)
                              Affected customers:
                              0 This affects my team
                              Watchers:
                              0 Start watching this issue

                                Created:
                                Updated:
                                Resolved: