Add worklog report summation per user and all

Reporting is a feature set that is currently entirely absent from this module. I have a long list of potential reports in a todo list.

Any idea how best to accomplish with minimal external dependencies?

Ideally this would transparently operate between display (with edit links, as you mention above) and printable modes, and would be sufficiently high-level that we could reuse code to build new reports.

I'm sufficiently old school that I used to do this sort of thing with MS Access or Crystal Reports...

No idea how this is done today!

While we're at it, my preference would be a separate burndown-reports module, especially if there's external dependencies.

I think it makes sense that reporting is a sub module. It's somewhat self-contained, and will likely ultimately be a large and complex module. It may also have a variety of external deps. In any case, we can add messaging / link on this module to the new reporting one.

I don't know if the timing part can be done that way though. It may need to be part of the main module. I don't have a strong opinion on the matter, just not sure.

As far as sums in views, the Views Aggregation module used to be how I did that. Not sure if that's the current state of things. It can do subtotals as well (i.e. if reporting on multiple people, it can subtotal under each one, then have a total at the bottom).

I'm glad somebody is using this module, and think it is benefiting greatly from your attention to detail. I haven't had the energy to do much other than bug fixes for a few years, so this is a big positive.

We can do it that way if you'd prefer.

Just thinking: we may need to add something to make the worklog entities properly accessible in Views. They're a custom field type, if I recall correctly. I probably should have just done entities for them...

Many years ago I built a time tracking system. The way it worked was that people entered their time into table 1. On a scheduled basis, a process ran that aggregated data into a separate set of tables. I'm not sure this is needed here (i.e. maybe views aggregation can do this), but it might be needed, particularly if the aggregated data needs to be stable (i.e. no changes after the weekly/monthly reports have run). Different companies have different requirements here, which likely adds some complexity.

Different companies track things differently. I've worked at companies that hire out devs or teams on a per-diem or per-week basis, and billing was tracked on those lines.

Wouldn't the time tracker go up in increments of 1 second though? And would it let the user round it up/down before saving?

I think overall the approach from your option #1 would make the most sense, since it would operate at a UI level (and hence respect any existing data), and would be logically associated with turning on the submodule.

I've approved the MR.

Think eventually we'll need to change "Hours" to a more explanatory title, and possibly move into a Reporting submenu. It's fine for now.

Once things stabilize, I'll have to go back and update the documentation for the project as well.

Merge seems to be stuck.

There's a substantial manual here: https://www.drupal.org/docs/contributed-modules/burndown

I think it's okay to have a README though.

Released on 1.0.72.