Content
View differences
Updated by Marc Alcobé 6 days ago
**As a** mobile app user
**I want** my in-progress comment text to be preserved when the comment input loses focus
**so that** I can temporarily switch context (e.g., look something up) without losing my work.
### Acceptance Criteria
* When the user types a comment and the comment input loses focus (tap outside, scroll down, open a different panel, navigate to another screen, switch apps, receive a call/notification), the typed text remains available when the user returns.
* The draft comment is restored exactly as typed (including line breaks, whitespace, emojis, and any mentions/markup supported by the editor).
* The draft comment remains preserved even if the user leaves the comment composer for “a second” and returns (quick focus changes).
* If the app is backgrounded and later resumed, the draft comment is still present.
* If the app is terminated (OS kills process) and relaunched, the draft comment is no longer preserved.
* If the user navigates away from the work package and later returns to the same work package, the draft comment is still present.
* If the user opens a different work package, the draft comment from the first work package does not appear in the second work package.
* Only one draft comment is maintained per work package.
* The user can only intentionally discard a comment by a new action added in the three dots menu of the comments toolbar called "Discard comment".
* No draft is saved for an empty composer (only whitespace) after focus loss (or it is saved but restored as empty; pick one and keep it consistent).
### Technical Notes
<br>
### Permissions and Visibility Considerations
* Only users with comment permission on the work package can post; draft preservation must not bypass permission checks.
### Translation Considerations
* Any new UI strings (e.g., “Draft restored”, “Discard draft?”, “Draft saved”) must be localised.
### Out of Scope
* Cross-device draft sync (server-side drafts) is not included.
* Version history of drafts.
* Attachment draft persistence (upload-in-progress preservation) is not included unless the current composer already supports it and requires explicit handling.
### Original feedback
When I am typing a wp comment and I need to look up something and leave the input field for a second the Iose everything that I have written so far. far\. Pretty annoying given that my memory got so bad that I constantly look up stuff three times.
times\.
---
Follow-up email: w.lindenthal@openproject.com
**I want** my in-progress comment text to be preserved when the comment input loses focus
**so that** I can temporarily switch context (e.g., look something up) without losing my work.
### Acceptance Criteria
* When the user types a comment and the comment input loses focus (tap outside, scroll down, open a different panel, navigate to another screen, switch apps, receive a call/notification), the typed text remains available when the user returns.
* The draft comment is restored exactly as typed (including line breaks, whitespace, emojis, and any mentions/markup supported by the editor).
* The draft comment remains preserved even if the user leaves the comment composer for “a second” and returns (quick focus changes).
* If the app is backgrounded and later resumed, the draft comment is still present.
* If the app is terminated (OS kills process) and relaunched, the draft comment is no longer preserved.
* If the user navigates away from the work package and later returns to the same work package, the draft comment is still present.
* If the user opens a different work package, the draft comment from the first work package does not appear in the second work package.
* Only one draft comment is maintained per work package.
* The user can only intentionally discard a comment by a new action added in the three dots menu of the comments toolbar called "Discard comment".
* No draft is saved for an empty composer (only whitespace) after focus loss (or it is saved but restored as empty; pick one and keep it consistent).
### Technical Notes
<br>
### Permissions and Visibility Considerations
* Only users with comment permission on the work package can post; draft preservation must not bypass permission checks.
### Translation Considerations
* Any new UI strings (e.g., “Draft restored”, “Discard draft?”, “Draft saved”) must be localised.
### Out of Scope
* Cross-device draft sync (server-side drafts) is not included.
* Version history of drafts.
* Attachment draft persistence (upload-in-progress preservation) is not included unless the current composer already supports it and requires explicit handling.
### Original feedback
When I am typing a wp comment and I need to look up something and leave the input field for a second the Iose everything that I have written so far.
---