What is the challenge? |
Can't visualize developer burnup using logged effort. I want the burnup chart to increment each time a developer logs effort. |
What is the impact? |
Improved capacity planning, especially for stories >1 sprint |
Describe your idea |
Title Expose individual time tracking log entries for reporting and export
Description As a product owner, I want each individual time tracking log entry (timestamp, user, duration, and comment) to be exposed as a first-class, reportable object so that I can:
Build reports that show one row per time log entry (rather than only the rolled-up Actual effort per feature/epic).
Analyze and visualize effort over time (e.g., per day, per week, by user, by team).
Export detailed time log data to CSV/Excel or external BI tools.
Access time log entries via the API for integration with other systems.
Today, I can only see these entries in the Time tracking UI on each record and report on the aggregated Actual effort field. I would like:
A reportable “time log” entity that includes at least: timestamp/date, user, duration, comment/description, and the parent record (feature/epic/release, etc.).
The ability to include these time log rows in list/pivot reports and charts.
The ability to export this time log data and access it via the API.
|