Missing possibility to define holidays for team members

We are currently heavily using Kunagi in our daily scrums. however we are really missing possibility to define holidays for per team member. Is it really missing in Kunagi? Or maybe it is possible - if yes, please help to find this out. If not - is it planned to be supported?

Statement from Kunagi Team

We will not do that for now. If this seems necessary after sto175 is done or it will come up otherwise, we will re-evaluate it.


Issue is closed.


Fri, Apr 27, 2012, 12:07 by artjom (PO,T)

Kunagi doesn't really do time-tracking on per-user basis. What would be the gain defining per-user holidays?

Mon, May 7, 2012, 09:56 by AdrianG

In fact not having possibility of defining per-user holidays is quite an issue in our team. We have multi-site teams where team members are located in few different countries which have different public holidays. This is visible mainly on burndown chart as slipping with our work and this is bit annoying cause it is noise in background which cannot be brought on top to be visible.

Mon, May 7, 2012, 11:50 by artjom (PO,T)

The question here is how this feature would work with the overall system. Ich we'd just make some UI to set per-user holidays, it would not automagically be incorporated into any other UIs. If only one Team Member has a free day, how would you "correct" a burndown or something to reflect this?

If it's just for information purposes, I'd suggest waiting for sto175. After we have the new calendar done, there will be more convenience features for it. At the moment the calendar is not really good. In fact, we do not use it ourselves.

Mon, May 7, 2012, 15:03 by AdrianG

"How?" it is good question. IMHO it would be nice to have something like factor for each day for ideal burndown. If every one are working it is 1. If one guy is out for given day, this factor could be (1 - 1/<team member count>), if two are out for that day it will be (1 - 2/<team member count>) and so on till we reach 0. This factor could be used to flatten ideal burndown for given day. This would simply reflect that team will be burning less at that day.

Outcome from this is pretty obvious for me, we would have more accurate info about how we are rolling at given sprint by one simple glimpse at burndown chart, without tinkering on the side to figure out whether there someone was out or whether on given day we really started to slipping with our work.

OFC integrating this with sto175 would be great. But IMHO it is not crucial.

Post a comment