burndown chart and original estimate for work prior to activating sprint?

[Ahmed Alghamdi]

as we are conducting technical grooming session for user stories planned for next sprint, we require some departments to avail some design documents so we can start to readify our APIs in order for development to be ready by front-end.

now, we discuss each user story and create all needed sub-tasks per story, but the sprint is not active yet, if i ask the team to start logging their working hours, and then activiate the sprint wouldn't this make data in burn-down chart not accurate? should we put original estimates to begin with? or shall we not log any work that takes place before the activation of sprint? don't know the best approach

[Ofira Daniel]

Team supposed to work only on issues which are part of its active sprint.

If team during sprint can take new issues , they should be added to active sprint and it will be reflected in your burndowm