Content
View differences
Updated by Marc Alcobé about 16 hours ago
**As** a user in a meeting \[enter role of user\]
**I want to** move an agenda item from one meeting to the next \[enter objective\]
**so that** I can tackle that topic in the next meeting of the series \[enter desired result\]
**Acceptance criteria**
* There is an action on the more menu of an agenda item to move this item to the next meeting.
* This is only available on meeting series
* Once the user taps on this the meeting item and all its information (including outcomes) are moved to the next meeting in the series. <br>
**Technical notes**
* To do that right now we need to do 5-6 API calls, which is not ideal.
* Can we reduce this or do we depend on the desktop backend team to improve this?
<br>
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** move an agenda item from one meeting to the next
**so that** I can tackle that topic in the next meeting of the series
**Acceptance criteria**
* There is an action on the more menu of an agenda item to move this item to the next meeting.
* This is only available on meeting series
* Once the user taps on this the meeting item and all its information (including outcomes) are moved to the next meeting in the series.
**Technical notes**
* To do that right now we need to do 5-6 API calls, which is not ideal.
* Can we reduce this or do we depend on the desktop backend team to improve this?
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._