Content
View differences
Updated by Jan Sandbrink 5 days ago
**As** a user \[enter role of LLMs, user\]
**I want to** have a tool to update work packages, \[enter objective\]
**so that** I can use my agent to update work packages from my inputs. \[enter desired result\]
**Acceptance criteria**
* A tool to update a new work package is available
<br>
**Technical notes**
* During update all business rules we'd usually enforce are enforced
<br>
**Permissions and visibility considerations**
* e.g. required fields
_To whom is this feature visible?_
* A correct `lock_version` must be provided for a successful update _When is it not visible?_
**Technical notes** **Translation considerations**
* We should probably stay compatible with _Key terms and phrases in the schema we usually accept for WP update via API key languages_
**Permissions and visibility considerations** **Out of scope**
* Regular permissions checks for <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the user performing the request are applied changes._
**I want to** have a tool to update work packages,
**so that** I can use my agent to update work packages from my inputs.
**Acceptance criteria**
* A tool to update a new work package is available
**Technical notes**
**Permissions and visibility considerations**
**Technical notes**
* We should probably stay compatible with
**Permissions and visibility considerations**
* Regular permissions checks for
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of