Tempo Ideas

In Jira Service Management, we use the Tempo worklog widget on service desk issues.
When logging time, our agents select a Tracker value in the widget. Tracker is a Tempo work attribute on the worklog, and we rely on it to categorise the type of work (e.g. billable vs non‑billable categories, internal vs external, or specific activity types).

Currently, the My Work → List view shows a fixed set of columns and does not allow us to display work attributes such as Tracker. This means:

• Agents can select a Tracker when logging time on the issue,

• But they cannot see that Tracker value later in their personal My Work → List view,

• They have to open detailed Tempo reports or exports just to verify which Tracker they used.

Request
Please add support for:

1. Displaying work attributes as columns in My Work → List, starting with the “Tracker” work attribute, and

2. Ideally, allowing admins/users to choose which work attributes appear as columns (similar to how columns can be added in Tempo reports).

This would make the My Work → List view much more useful as a daily timesheet view, especially for users who log time from JSM issues using work attributes.

Why this matters

• Our support and implementation teams work primarily in Jira Service Management and log time directly from the issue using Tempo’s widget.

• They must select a Tracker so we can later report accurately on what type of work was done.

• Agents want a simple, personal view (My Work → List) where they can:

  • Review their week’s worklogs,

  • Confirm the Tracker selected is correct, and

  • Correct any mistakes quickly.

• Today, the only way to see Tracker per worklog is to:

  • Build a Tempo report with Tracker as a column, or

  • Export data for further analysis.

• This is overkill for a user who just wants to quickly check: “What did I log, and which Tracker did I pick?”

Adding work attributes as optional columns in My Work → List would:

• Reduce errors in how work is categorised,

• Make it easier for users to validate their own logs,

• Improve adoption of work attributes without forcing everyone into complex reports.