docs: sync ticket workflow stage progress
This commit is contained in:
@@ -37,6 +37,17 @@ Frontend:
|
||||
- Create: `frontend/src/features/tickets/TicketTransitionDialog.tsx`
|
||||
- Create: `frontend/src/features/tickets/TicketMetaPanel.tsx`
|
||||
|
||||
## Implementation Progress
|
||||
|
||||
As of 2026-07-03, Stage 1.7 has moved beyond the first visual redesign into a stronger ticket workflow baseline:
|
||||
|
||||
- Ticket categories are standardized as `业务问题`, `技术问题`, `数据问题`, and `操作问题`.
|
||||
- Category-driven status policies shorten simple business/operation tickets while preserving the full technical workflow.
|
||||
- Ticket creation captures business-facing context fields including problem performance, problem object, submitter, submitter organization, and environment.
|
||||
- Solution adoption can close a ticket, write the resolution summary, update usage count, and record timeline events.
|
||||
- Recommended linked solutions remain non-closing references, but resolve/close dialogs prefill the resolution from linked solutions.
|
||||
- Ticket detail side metadata was reduced to avoid repeating the overview card.
|
||||
|
||||
## Task 1: Backend Ticket List Support
|
||||
|
||||
**Files:**
|
||||
|
||||
Reference in New Issue
Block a user