Where should we log work during iteration planning?

Erwin Saegesser

Hi Jira (or Greenhopper) Team -

After an evaluation phase we've now introduced Jira/Greenhopper to a first dev team. All works fine and we have setup the project.

What we want: We want to log work during iteration planning (and grooming) as well as during the iteration itself. The latter is well understood and we don't see an issue (estimated/work/remaining etc.).

Problem: Where can we log work during the whole planning and grooming phase? Do you have any best practices? We found that we could log work for stories (the tasks would be to used to log work during the iteration). But what about general discussions which aren't related to a single story? Example: We spent (3 devs) one morning organizing and grooming our backlog. We created releases and dates etc.. Where would we log that work?

Remark: I'd like to avoid logging all the work in our ERP (in addition to what we log in the tasks).

Thanks in advance,
Erwin

Ivar

We created a 'Generic time tracking' issue type and creates Planned leave, Sickness, Sprint Planning, etc., for every sprint. People log the time used on these tasks and since they have fix version set for the given sprint, time is logged per iteration. Works like a charm for us.