**As** a contributor writing long texts, e.g. work package descriptions or comments
Begin of the insertion**When** experiencingEnd of the insertion Begin of the deletion **I want to** keep my unsaved inputs (let's call them drafts) even when the page closes or theEnd of the deletion browser crashes Begin of the insertionor any other reason that kills my editor instance (happened to me latelyEnd of the insertion Begin of the deletion
**so that** I don't lose these messages (and loseEnd of the deletion a lot Begin of the insertionunfortunately)
**When re**loadingEnd of the insertion Begin of the deletion of time)

**Acceptance criteria**

* When composing/editing a work package description or comment and I killEnd of the deletion the Begin of the insertionpageEnd of the insertion Begin of the deletion browser process, and I restart the browser and open the same URL, it will preload the input fields forEnd of the deletion with the Begin of the deletion drafted value.

* When I save the work package, comment, wiki page,... the draft is removed.

* After X days the (let's say a week) drafts also get discarded in order to not pollute the browser's local storage too much.


The technical idea is assigning everyEnd of the deletion rich text Begin of the insertioneditor
**I want to**End of the insertion Begin of the deletion input field (a field that uses CKeditor) something like a URN. The URN could serve us as a key in the browser's local storage to identify that input field's drafted value.

So for example

* the draft for the description of a new work package couldEnd of the deletion have the Begin of the insertioneditor pre-filledEnd of the insertion Begin of the deletion URN `work_packages/new/description`

* the draft for the description of an existing work package (ID 54) could have the URN `work_packages/54/description`

* the draft of a comment for work package (ID 54) could be `work_packages/54/comment`

* Similar for meetings agendas and minutes, wiki pages etc.


When a user starts composing a message, it will continuously save the current value in the local storage using that URN as the key.

Every time the front-end renders it will check for relevant URNs and change those fields into edit mode and prefill itEnd of the deletion with the Begin of the insertionlast autoEnd of the insertion Begin of the deletion value that wasEnd of the deletion saved Begin of the insertiontext
**so that** I don't need to learn/findEnd of the insertion Begin of the deletion as draft inEnd of the deletion the Begin of the insertionoption to choseEnd of the insertion Begin of the deletion local storage.

Every time a field gets savedEnd of the deletion the Begin of the insertion"time machine" icon fromEnd of the insertion Begin of the deletion value inEnd of the deletion the Begin of the insertioneditors toolbarEnd of the insertion Begin of the deletion local storage gets removed.

**EXTRA:**

We could also store the drafts on the server that a user can start working on a text on one deviceEnd of the deletion and Begin of the insertionselectEnd of the insertion Begin of the deletion then continue working on a different device. However, that is a different usage scenario and I believe it complementsEnd of the deletion the Begin of the insertionlatest saved version.End of the insertion Begin of the deletion local storage approach.End of the deletion