Comment 2 for bug 1185041

Sorry for responding to this so late!

Some sort of per-project subdivision sounds like a useful feature. However I don't want to rush and accept the first patch, since multiple people have expressed wishes for related things (tags, subcategories), and I wouldn't want to end up with a mismash of features that don't work together well. (That's why I ignored this bug report for so long -- but I should've said so at the beginning, and not procrastinated writing a response.)

I'd like to see concrete examples of these things you call phases. Would that be things like planning, design, implementation, testing? I'd also like to see a concrete small example of daily/weekly/monthly reports that include these.

I'm not a fan of configuration options that change the interpretation of data files. (E.g. virtual_midnight was a mistake: change it and you can get incorrect reports for past dates.)

I'm not very comfortable about passing the entire settings object to the TimeLog/Reports classes, but I cannot articulate why that feels wrong.