Group the Summary by epic and feature

Version 2.0.50 · Coming next · All release notes

A small addition to the Time Log Summary for teams who plan in epics and features: the grouping now follows your backlog all the way up. There’s nothing you need to do — it’s there the next time you open the page.

🌳 Group the Summary by Epics, Features and Stories

Your process’s backlog levels join the levels you can tick and drag into your Summary grouping. Time is usually logged against tasks, and Parent only reaches the item directly above them; the new levels reach the stories, features and epics above that, so the Summary can answer “how much went into this epic?” in one search.

The levels are read from each project’s own backlog setup and named after it — Epics, Features and Stories on the Agile process, Epics and Issues on Basic, and any level your organisation has added. Time rolls up to the right item whatever it was logged against: a task under a story, a bug directly under the feature, or the feature itself. Time on work items with nothing on a level above them is gathered under No User Story, No Feature, No Epic and so on. A search across projects on different processes groups same-named levels together. Parent is unchanged, and still groups by the item directly above, whatever its type.

The CSV export gains an id and a title column for each level — added at the end, so a spreadsheet built on the existing columns keeps working.

With the grid nesting deeper, the coloured squares beside each row are gone. Rows for a user, project, area path, iteration or time type now show a small grey icon for what they group by, and work items keep their own type icon.

Full change list

2.0.50

Time Log Summary: group by your backlog levels, so time logged on tasks rolls up to the stories, features and epics above them. The levels come from each project’s own backlog configuration and are named after it — Epics, Features and Stories on the Agile process, Epics and Issues on Basic, plus any level your process adds — and sit just above Parent item, top level first, so ticking them nests the grid the way the backlog does. Time rolls up to the right item whatever it was logged against: a task under a story, a bug directly under the feature, or the feature itself. Work items under no item on a level are gathered under No User Story, No Feature, No Epic and so on. When a search spans projects on different processes, levels with the same name are grouped together (Basic’s Epics with Agile’s), and a level each names differently shows both names. Parent item is unchanged: it still groups by the item directly above, whatever its type. The CSV export gains an Id and a Title column per level, added at the end so existing spreadsheets keep working. The coloured squares beside each row are gone: rows for a user, project, area path, iteration or time type show a small grey icon for what they group by, and work items keep their type icon.