CT-Ops

DSUM

Operator guide for CT-Ops daily stand-up pages, team boards, engineer views, actions, comments, and schedule controls.

The DSUM menu item opens /dsum. Use it to run daily stand-ups for configured engineering teams, keep open team tasks visible, assign follow-up actions to engineers, and review previous stand-up records.

DSUM is membership-scoped. A user only sees teams where they are a member. Administrators configure teams and membership in Engineering Teams. DSUM records are instance-scoped, and all edit actions require instance write access.

Page order

In the CT-Ops main menu, DSUM is an ITIL menu item alongside Incidents, Services, and CMDB. The documentation page is listed with the other top-level CT-Ops pages.

DSUM index

The index page lists the daily stand-ups for the engineering teams that include the signed-in user. Use it at the start of a handover to choose the right team board or to reopen a recent stand-up for reference.

The summary cards at the top show:

DSUM team table

The DSUM table is the primary launch point.

The favourite button is disabled while its save is in flight. If the update fails, the page keeps the previous order and state.

Previous DSUMs table

When recent history exists, Previous DSUMs lists the latest visible DSUM records.

The index loads up to 30 previous stand-up records across the current user’s visible teams.

Team DSUM page

The team page opens at /dsum/<teamId>. It is the working stand-up surface for one engineering team and one DSUM date.

The header shows a back button to DSUMs, the team name, and whether the selected DSUM exists. When the stand-up exists, the header states who started it and the DSUM date.

The page refreshes itself through a server-sent event stream every 2 seconds so multiple operators can see task, action, and comment changes without manually reloading.

Team summary cards

Date and history controls

The Previous DSUM date field is a date input backed by the team’s last 30 DSUM dates. Selecting a date from that history navigates to the historical record. Manually typing a date that is not in the loaded history does not navigate.

Historical DSUMs show a View only badge. CT-Ops enforces this on the backend: edits are rejected unless the selected DSUM date is today’s date in the DSUM’s stored timezone.

Start stand-up

When today’s DSUM does not exist, Start stand-up opens the Start DSUM dialog. Use it to create the daily board and optionally place the stand-up on the operations calendar.

Starting a new DSUM rolls open tasks and open actions forward from the team’s most recent earlier DSUM. Completed tasks and completed actions are not rolled forward. Rolled-forward items preserve their original creation dates and keep metadata pointing to the source DSUM.

Edit schedule

When today’s DSUM already exists, Edit schedule opens Edit DSUM schedule. Use it to correct the start time, end time, or recurrence for the calendar event attached to the stand-up.

The fields match Start DSUM, except the stand-up date itself is not edited. Saving updates the linked operations calendar event and its participants. Team members are calendar participants; the saving user is stored as owner and other team members are observers.

Create task

Create task appears after a DSUM exists. Use it for a topic, risk, handover item, or follow-up that the team needs to track during the stand-up.

If the backend receives a create-task request for today’s date and the DSUM row does not exist yet, it creates the DSUM row automatically before creating the task.

Board tab

The Board tab is the default team view. It is for running the stand-up around tasks first, then drilling into actions and comments for the selected task.

Board filters

Task sections

The board groups tasks into stable sections:

Each section header shows the number of visible tasks in that section. Empty sections show an empty-state message.

Task table

Rows can be selected with a pointer or by focusing the row and pressing Enter or Space.

Task detail panel

The detail panel shows the selected task. Use it to update the task, manage its actions, and record notes.

The header shows task status, creator, and creation time. The description is shown below the header when one exists.

Edit task

The Edit task dialog has the same Item title and Context, notes, or desired outcome fields as task creation. Saving updates the task title and description and records an audit event.

Task engineers

The Task engineers panel is derived from the task’s actions:

View actions

View actions opens a dialog containing the action table for the selected task.

Create and edit actions

Use actions for specific follow-up work under a DSUM task. Actions are the units assigned to engineers.

The engineer lists include active users in the current instance, not only DSUM team members. Operators should usually assign team members unless another engineer is deliberately helping with the task.

Action status and deletion

Marking an action complete requires an explicit confirmation because completed actions can disappear from default engineer filters.

Notes and comments

Task notes and action comments keep stand-up context with the work.

Task status changes create internal comments such as Item marked completed. Action status changes create internal comments such as Action marked open. Action detail hides these status comments from the normal comment list and shows them under Action history.

Action detail dialog

Selecting an action row opens the action detail dialog.

Use action detail during handover when the table title is not enough to explain the state of the work.

Engineers tab

The Engineers tab is for checking individual load and ownership. Use it near the end of stand-up to confirm every engineer knows their actions and to spot unbalanced work.

Engineer list

The left list contains active members of the DSUM’s engineering team, sorted by display name.

Selecting an engineer opens their detail panel.

Engineer actions

The Actions subtab shows actions where the selected engineer is primary or secondary.

The action table includes the Task column so an engineer can see which task each action belongs to.

Engineer tasks

The Tasks subtab shows tasks where the selected engineer is the derived primary engineer.

Each task card shows the title, count of open actions, creator, status, and the same edit, complete/reopen, and delete controls used by the Board tab.

Read-only history

A DSUM is editable only when its standupDate equals today’s date in the stand-up timezone. Historical DSUMs are read-only in both the UI and backend.

On read-only records, CT-Ops disables task creation, task edits, task status changes, task deletion, comments, action creation, action edits, action status changes, and action deletion. Use history for handover, audit, and reviewing what was agreed on earlier dates.

Access and membership rules

DSUM requires instance write access. Team data is additionally scoped through engineering team membership:

Administrators manage the available teams and team members in Engineering Teams.

Calendar behaviour

When a DSUM has both a scheduled start and end time, CT-Ops creates or updates an operations calendar event titled <team name> DSUM. The event description contains the team name and DSUM date. The event timezone is the browser timezone sent when the schedule is saved.

If either start or end time is missing, CT-Ops does not create a calendar event. Editing the DSUM schedule later can create or update the event.

Data retention and deletion behaviour

DSUM history is retained in the database as stand-up records, tasks, actions, and comments. The UI currently loads the latest 30 history dates for the team page and the latest 30 previous stand-ups for the index.

Deleting a task deletes its actions and all comments linked to the task or its actions. Deleting an action deletes comments linked to that action. These delete actions are permanent from the DSUM UI, so use them for mistakes rather than normal completion.