Skip to main content

3.6 Query and feedback (/releases)

Search: date / ticket number / deployer → "Query" loads the list; clicking a row expands the detail panel.

momo-cogwork directmomo-ticket-system connectionconnected by bothblocked / guardedsolid = relation · staticdashed = traffic · animated Query release recordsClick a release ticketDetail paneldetails / merge results / status historyDEPLOY_USER / ADMINRole = Deploy_User / Admin?Test / production mergeRelease feedbackstatus·urgent·rollbackTrigger deployJenkinsyesEdit detailsbranch / engineer / count / path / orderDeployment window · apply / clearDeployment dependency · add / remove

Figure 7 — Action branches of the query page's detail panel

Release feedback (PUT /releases/{id}/feedback)​

FieldNotes
Release completed?dropdown: not released / released / cancelled / failed / deploying / deploy succeeded / deploy failed
Urgent release?when ticked, "urgent reason" becomes required
Rollback?when ticked, "rollback reason" becomes required

Urgent / rollback exist as two independent copies — one set at creation (release type) and one at feedback — so after the release they can be re-declared or corrected through feedback. The momo-cogwork release-feedback feature (§2.3) writes the same data over the ext API.

Details table (editable in place)​

Columns: order / system / branch / development engineer / program count / config path / notes + an edit button.

Editable fields: branch, development engineer, program count, config path, notes and order (sortOrder, numeric) — added 2026-07-08, so the person who filed the ticket can adjust the display order of the details themselves.

Edit permission: Admin can always edit; other users can only edit release tickets they created that have not yet merged successfully.

Other blocks​

BlockNotes
Test merge / production mergePOST /releases/{id}/test-merge, POST /releases/{id}/merge (production merge asks for a second confirmation). Returns GIT_CONFIG_REQUIRED when the Git settings are missing
Trigger deployshown only when the ticket's system has Jenkins jobs configured; POST /releases/{id}/trigger-deploy; the deploy result is written back asynchronously by the Jenkins pipeline over the API-key callback
Deployment windowpick an existing window from the dropdown → apply (PUT /releases/{id}/window)
Deployment dependencysearch a ticket number → add / remove a dependency (this ticket must wait until the dependency ticket completes before it can deploy)
Status historyevery status change is recorded and shown as a timeline
Merge resultsstatus / commit / conflict content shown per branch

This page has no export function (the Excel template download exists only on the release-form page).