**As** a meeting faciliator or participant
**I want to** be able to convert an agenda item into a work package
**so that** I can easily make agenda items actionnable in a project context

**Acceptance criteria**

* Add a new option in the 'More' menu of basic agenda items

* Label: "Convert to work package"

* Leading icon: `op-work-packages`

* When this option is clicked, open a work package creation dialog

* Begin of the insertionUse the existing dialog for creating a new child

* End of the insertion The project should be the project the meeting belongs to Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * The subject should be the title of the agenda item Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * The type should be the first item on the list Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * The description should be the contents of the note Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * If meeting outcomes exist, they should be appended to the description Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Only the basic and required fields should be present Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Basic fields include: subject, description, type, assignee and date Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Other non-required fields (status, priority, version...) are not present Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * After the user clicks on 'Create work package', the modal is closed and the agenda item is converted to a work package agenda item

* \[open\] Do we still display the agenda item notes (now the description of the work package) as is? Pro: the user has the current context; Con: duplication.

* Possible solution: include the work package description as a macro.


**Technical notes**

* <br>


**Permissions and visibility considerations**

* None


**Translation considerations**

* New string: &#39;Convert to work package&#39;


**Out of scope**

* to be explroed