35 lines
914 B
Markdown
35 lines
914 B
Markdown
# 08 Ticket Details, Editing, and Worklog
|
|
|
|
## Goal
|
|
|
|
Provide a ticket detail view where ticket data can be reviewed and edited, and where the full change history is visible.
|
|
|
|
## Requirements
|
|
|
|
- Provide a ticket detail page per project ticket.
|
|
- Show and allow editing of:
|
|
- title
|
|
- description
|
|
- acceptance criteria
|
|
- type
|
|
- priority
|
|
- custom field values
|
|
- Add a worklog timeline to the ticket detail page.
|
|
- Every ticket change must create a worklog entry with:
|
|
- actor
|
|
- timestamp
|
|
- change summary
|
|
|
|
## Acceptance Criteria
|
|
|
|
- Editing any tracked ticket field creates a new worklog entry.
|
|
- The worklog clearly shows who made each change.
|
|
- Users without project `edit` permission cannot update ticket details.
|
|
- Users with project `view` permission can still open the ticket detail view.
|
|
|
|
## Out of Scope
|
|
|
|
- Rich-text editing
|
|
- Mention notifications
|
|
- Separate comment threads
|