A tidier Time Log Admin page

Version 2.0.49 · Latest · All release notes

This release tidies up the Time Log Admin page, where your administrators manage time types and settings. It is easier to find your way around, clearer about what has and hasn’t been saved, and safer when you change which Time Log API your organisation uses.

At a glance

• 🗂 Time types by project — with a filter, and a dot for active or disabled
• ⚙ Settings grouped by what they do — each with its description beside it
• 💾 A save bar — that says what hasn’t been saved, with a new Discard
• 🔑 Per-user sign-in — the API connection says whether it is on
• ℹ About — the version and organisation ID in one place

🗂 Time types, grouped by project

Time types are now listed under their project, All projects first, with a count for each. A green or red dot beside each name shows whether it is active or disabled, and each project’s default carries a Project default tag. Type in Filter time types to find one by name, or untick Show disabled to hide the retired ones. New time type opens the form in a dialog.

⚙ Settings grouped by what they do

The settings are grouped under API connection, which now comes first since nothing else works until it is set, then Time entry, Work item updates, People and Summary, targets and timer. Each one’s description is shown beside it rather than hidden in a tooltip, and on/off settings are switches.

💾 Never wonder whether you saved

A bar at the bottom of the window says when there are unsaved changes, with Save settings and a new Discard that puts everything back as it was last saved. Changing a setting and changing it back again leaves nothing to save, and a save that fails says why. A new API key or URL takes effect once it is saved, not while it is being typed, and saving it reloads everything from the new API. The weekly target and Include ADO days off are never saved over that API’s own values unless they loaded from it first.

🔑 Per-user sign-in, at a glance

API connection now says whether per-user sign-in is on for the API your organisation uses and, if it isn’t, how to ask us to turn it on. With it on, the extension no longer sends your organisation’s API key alongside each person’s own sign-in, as the API doesn’t need it.

ℹ Version and organisation ID under About

The version and your organisation ID, the two things we ask for when you contact support, are now under About at the top right of the page, with a button that copies the ID and a link to the documentation.

Full change list

2.0.49

Time Log Admin: a tidier page. Time types are grouped by project, each showing a Project default tag and a green or red dot for active or disabled, with a filter and a Show disabled switch; New time type opens the form in a dialog. The settings are grouped under API connection (now first), Time entry, Work item updates, People and Summary, targets and timer, each with its description shown rather than in a tooltip, and on/off settings are switches. A bar at the bottom of the window says when there are unsaved changes, with Save settings and a new Discard. API connection says whether per-user sign-in is on for the API the URL points at, and how to get it. The version and organisation ID move into an About panel, with a link to the documentation. Saving is safer too: the extension uses the Time Log REST API Key and URL as saved, not while they are being typed; saving a new URL reloads everything from the new API; a failed save says why; and the weekly target and Include ADO days off are never saved over the API’s own values unless they loaded from it first. With per-user sign-in on, the extension no longer sends the shared API key alongside each person’s own sign-in.