fixed
This commit is contained in:
@@ -302,3 +302,20 @@ The module should keep tests around:
|
||||
- Reference sequence collision prevention.
|
||||
- Browser spellcheck attributes on writable fields.
|
||||
|
||||
|
||||
## Rich Editor, Spellcheck, Clear and Close Workflow
|
||||
|
||||
The ticket create and reply forms use rich HTML editing controls. Do not replace the rich editor with a plain `<textarea>` to enable spelling suggestions. Spellcheck must be enabled on the actual `contenteditable` editor surface using `spellcheck="true"`, `lang="en-GB"`, `autocorrect="on"` and `autocomplete="on"`.
|
||||
|
||||
Browser spell suggestions appear inline as red underlines and are selected from the browser context menu by right-clicking or Ctrl-clicking the misspelled word.
|
||||
|
||||
The create-ticket **Clear** action must only clear transient user-entered content:
|
||||
|
||||
- subject
|
||||
- details/body
|
||||
- tags
|
||||
- attachments
|
||||
|
||||
It must preserve configured routing defaults such as company, board, priority, category, project, team and due-date defaults.
|
||||
|
||||
When a user selects a closed ticket status, the professional closure modal must open on the first interaction. A closure comment remains mandatory, and the user can choose whether the closure comment is public or internal.
|
||||
|
||||
Reference in New Issue
Block a user