iceScrum | Select a wider range of dates for Burndown chart in Sprint – iceScrum

iceScrum Forums Discuss on iceScrum

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

  • Author
    Posts
  • #34905

    jlabuelo
    Participant

    Hi all

    We are starting to use IceScrum, and as usual in this cases we are starting to face some situations we dont know how to solve.

    For excample this time we are checking the burndown chart in hours for an sprint that is longer than a week, but chart only shows evolution starting 7 days before. If we have set up our sprints for two weeks… how can we configure Icescrum to show the complete evolution of the sprint and not only the last 7 days?.

    Thanks a lot in advance.

    Regards

    #35058

    Nicolas Noullet
    Keymaster

    Hi,

    The chart should match the sprint actual duration (from activation to closing) and don’t match the manually entered “start date” and “end date”. The former are the boundaries of the period where updates can occur in the sprint, whereas the latter are only expected dates.

    That may be the reason why the dates don’t match what you expect?

    #35067

    jlabuelo
    Participant

    Hi Nicolas

    Thanks a lot for your answer. Yes you are right “last date” is the actual date as the sprint is no closed, however “start date” in the chart for the sprint seems not to be the “activation date”, but the date the first task has been set to “done”.

    We have launched a sprint on 27 of August (setting it to active), but the first date in the chart is the 30th as it seems it was the date the first task has been moved to “done”. (in case this helps you someway).

    Thanks a lot once more!

    #35505

    Nicolas Noullet
    Keymaster

    Hi,

    Thanks for your feedback!

    The first point is expected to be recorded at sprint activation so the behavior you describe is unexpected. We will investigate.

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

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