manops - Manager cockpit

New focus: client-facing vs internal work. manops is pivoting to a top-down client vs internal lens (see the Client work and Internal work tabs). Some figures are placeholders pending a JIRA restructure (UCP splits into Client Projects CP and Internal Projects IP) and the proposed billing tool. Those are marked below and on each tab.

Active clients

live client desks

Techs logging

Client vs internal -

click Client-facing or Internal to drill in

Work	Created	Closed	Open	Hours
Client-facing client desks →
Internal Unison desks →
Project work (UCP) pending CP/IP
Total

Client share of logged hours: . Created drops ex-clients unless "include ex-clients" is ticked; Open is current-state (excl VM). Project work (UCP) will split into CP (client) + IP (internal) once the JIRA restructure lands.

Client-facing work. Client service desks plus, once the restructure lands, Client Projects (CP). Internal / Unison work (incl. the UI desk) has its own tab. SNOW-report analytics (cause trending, reopened, type mix, escalated) moved to the Archive tab.

Resolved

Created

Hours logged

Unresolved

Backlog trend (created vs resolved)

Net this month:

Client by client (this month)

client desks - click a client to drill in

Client	Created	Closed	Open	Hours

Client Projects (CP)

pending

Pending the JIRA restructure. Once UCP splits, client project work (resolved / open / hours) shows here, separate from internal projects (IP, on the Internal work tab).

Per-client time & contract

pending

Hours logged per client this month, each client's billing arrangement (from the proposed avrilbot tool), and whether they are within / above / below contract expectations. Needs a per-client time metric and the billing tool.

Open by status

No open tickets.

Open by priority

No open tickets.

Client vs internal time - last 30 days

interim split

Client desks

hrs

Internal (UI desk)

hrs - UI desk only

Other (projects/UCP)

hrs

Client share

of logged time

Seeds the client-vs-internal lens. Interim: only the UI desk is counted as Internal here - other internal desks and UCP project work fall into Other until the split is driven off the full internal set and UCP splits into CP/IP.

Internal (Unison) work. Internal / system desks (incl. the UI desk: AH, BAK, CT, GEN, HSE, UH, UI, UR, UTO, VM) plus, once the restructure lands, Internal Projects (IP). Figures below are interim, from the current hours breakdown, until the UCP split.

Internal hrs (mo)

Unison/internal, incl UI

Client hrs (mo)

for contrast

Project hrs (UCP)*

pending CP/IP split

Total hrs (mo)

all logged

Internal by project / desk (this month)

project-by-project comparison

Project / desk	Created	Closed	Open	Hours

No internal work this month.

Internal / system desks plus UCP project work. Once UCP splits into CP + IP, the internal project rows become IP and client project work moves to CP on the Client work tab.

Internal Projects (IP)

pending

Once UCP splits into CP and IP, internal project work gets its own clean line (currently folded into the UCP row above).

Tech activity through the client vs internal lens. Are techs servicing clients or doing internal work? Hours and open work below; the per-tech client-vs-internal time split is a placeholder until the classification split lands.

Logged hours this month, by tech

Goal h (%) · available h/mo · green on trend, red behind

Open tickets per tech

client desks - click a tech

Tech	Open	High/Highest

None.

Open project work per tech

UCP - pending CP/IP split

Tech	Open	High/Highest

None.

Client vs internal time per tech

pending

Each tech's logged hours split into client-facing vs internal work, to answer "who is on client delivery vs internal projects?". Needs the client/internal classification split.

- ()

Loading…

Key	Summary	Status	Priority	Time spent

No open tickets.

Backup health unavailable:

manops calls bart server-to-server with a dedicated service account. Set BART_USER / BART_PASS to enable.

As at , -day window. Click a client for its jobs.

- backup jobs

view in bart ↗

Loading…

Health	Job	Type	Schedule	Last night	Fails (7d)

Loading…
No jobs.

Upcoming license renewals (next 30 days)

Source: JSM Renewal Register (LR) project.

Key	Summary	Due	Status	Owner

Nothing due in the window.

Upcoming scheduled work (next 30 days)

Any open ticket with a due date in the window (excludes renewals above).

Key	Summary	Due	Status	Created	Owner

No scheduled work due in the window.

Staff leave

Planned tooling, not yet implemented. Will surface upcoming staff leave from myhr (Xero) alongside the operational views.

Staff movements

Planned tooling, not yet implemented. Will be pulled from a shared team calendar (onboarding, offboarding, role changes) once available.

Endpoint uptime monitoring

Planned. A dedicated uptime-monitoring tool needs to be built first, exposing an API; manops will then pull that data in (like it does bart), rather than monitoring endpoints itself.

ScubaWatch reports

Planned (TBC). Will surface ScubaWatch reports here once the data source / API is defined.

Shepherd stats

Planned (TBC). Will surface Shepherd monitoring/alert stats here once the data source / API is defined.

Billing visibility. The planned flow: a "to be billed" flag on the Jira ticket; when the ticket is closed with it checked, the ticket lands in the queue below. Client billing arrangements (full managed / partial / ad-hoc / prepaid bucket) will live in the proposed avrilbot tool so a tech can check "does this need billing?" at ticket creation.

To be billed (flagged, closed)

pending

Pending a new Jira "to be billed" field (distinct from the existing Invoiced field). Closed tickets with the flag checked will queue here for invoicing.

Ad-hoc invoicing candidates

Candidates

To invoice

Invoiced

Billable hrs

Ad-hoc invoicing candidates

Read-only. Resolved tickets with logged time; "Invoiced" is the authoritative Jira field.

Key	Client	Summary	Hours	Invoiced

Monthly meeting -

Reports on . Manual sections seeded from .

Auto metrics (from JSM) - "last mo" =

Ops resolved
Ops created
Ops hours
Unresolved

Project resolved
Project open
Escalated (approx)
Cause blank
Time Spent (approx)

Manual sections (editable, seeded from last month)

Confluence storage markup

Create a new page titled in the UITS space, switch the editor to source/storage view, and paste.

Archive. Cards moved off the main flow during the client/internal pivot, kept here so they can be pulled back: the cross-tool snapshot, data health and backup summary from the old Overview, plus the SNOW-report analytics. Ticket-stat and analytics figures reflect the current Client work filter scope.

Cross-tool snapshot (from the old Overview)

Renewals (30d)

Backups failing

UTO tickets (mo)

created

Devices (MeshCentral)

unavailable

Data health

synced min ago ()

Issues cached

Worklogs

JSM / Jira

Open w/o status cat.

No data-quality warnings.

Backup health

View all →

Ops ticket stats & analytics (whole scope)

Statistics reporting

approx

Escalated ↗
Cause of issue blank ↗
Time Spent (no time logged) ⤢

Cause-blank & Escalated link to their live Jira filters; Time Spent lists the zero-time tickets here (Jira has no "time spent = 0" filter).

Resolved (mo)

Created (mo)

Unresolved

Loading…

Key	Summary	Status	Owner	Time spent

No tickets.

Ticket type mix (created this month)

None created this month.

Reopened / bounced tickets

Reopened this month
Reopened & still open
Ever reopened (scope)

Cause of issue trending (resolved, last 6 months)

Cause	Total

No resolved tickets in range.