iceScrum | Inconsistencies in Sprint Dates – iceScrum

iceScrum Forums Discuss on iceScrum

Viewing 2 posts - 1 through 2 (of 2 total)

  • Author
    Posts
  • #13140

    Caroline
    Participant

    Hi,
    I have seen some inconsistencies in the start and end dates in the UI as well as what the REST API returns.

    For example:
    In the GUI sprint plan I see these dates:
    06/02/2015 – 06/15/2015

    In the GUI Release plan, I see these dates for the same sprint:
    06/02/2015 – 06/15/2015

    If I then Update the sprint via the Release plan with the GUI, I see these dates:
    06/03/2015 – 06/16/2015

    The REST API returns these dates for the same sprint:
    activationDate: 2015-06-03
    endDate: 2015-06-16
    startDate: 2015-06-03

    Is there a reason for these differences? Do they mean anything different?

    #14381

    Nicolas Noullet
    Keymaster

    Hi Caroline,

    Sorry for the late answer. Actually I have written an anwer before but it seemed that I never submitted it.

    This is a nasty long standing bug that affects projects which timezone is before UTC (which I assume is your case?). Sprint dates are mistakenly converted to the project timezone when they are displayed in the Sprint plan / Release plan, that is why they are shown one day before the date actually stored in iceScrum (the date shown in the Update / REST API).

    This issue should definitely be solved! However, many teams rely on the displayed dates, which are wrong, and fixing them will probably cause some trouble.

Viewing 2 posts - 1 through 2 (of 2 total)

The forum ‘Questions and help’ is closed to new topics and replies.