Content
View differences
Updated by Hagen Mahnke 10 months ago
**As** a user \[enter role of user\]
**I want to** have some useful types for creating a directly edited, collaborative document \[enter objective\]
**so that** I can better use documents for standard use cases \[enter desired result\]
**Acceptance criteria**
* Seed document types
<br>
**Technical notes**
* **Standard** \[name TBD; directly edited & collaborative\]
<br>
**Permissions and visibility considerations**
* Statuses: `New`, `In progress`, `Finalised`
_To whom is this feature visible?_
* **Specification** \[directly edited & collaborative\]
_When is it not visible?_
**Translation considerations**
* Statuses: `New`, `Ready for review`, `In review`, `Approved`, `Finalised`, `Rejected`
* **Contract** \[directly edited & collaborative\]
* Statuses: `New`, `Ready for review`, `In review`, `Approved`, `Signed by company`, `Signed by all parties`, `Rejected`
<br>
**Translations**
Need translations for the seeded document type names _Key terms and phrases in the statuses.
<br>
key languages_
**Out of scope**
* Editing types and their statuses in UI
* Status transition and other workflow rules <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** have some useful types for creating a directly edited, collaborative document
**so that** I can better use documents for standard use cases
**Acceptance criteria**
* Seed document types
**Technical notes**
**Permissions and visibility considerations**
**Translation considerations**
* **Contract** \[directly edited & collaborative\]
* Statuses: `New`, `Ready for review`, `In review`, `Approved`, `Signed by company`, `Signed by all parties`, `Rejected`
<br>
**Translations**
Need translations for the seeded document type names
<br>
* Editing types and their statuses in UI
* Status transition and other workflow rules
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._