Content
View differences
Updated by Wieland Lindenthal about 1 month ago
**As** a project member
**I want to** move a document to a different project
**so that** I can reorganize content across projects without having to recreate it manually.
**Acceptance criteria**
* There is a "Movo A "Move to another project" action in is available from the three dots menu
* in document view (e.g. via the documents list and
document's action menu).
* in the document itself
* Selecting it opens a project selector dialog (reusing the existing "move project" flow where applicable).
* Comment by WL: I am not sure what that means. The work package move is a very sophisticiated screen in which the user can change other attributes and even leave a comment. That is not the case for documents. We should keep it simpler here.
* Only projects that have the Documents module enabled are shown in the selector.
* Also On confirmation, the current user needs to have the permission to manage documents in the target project.
* When a target project is selected and confirmed:
* When originally triggered from within the document:
* The document is removed from the current project and appears in the selected project. The document is reopened in the other project context.
* A success banner is shown
* When originally triggered from within the documents lists:
* The document is removed from the list
* A success banner is shown
**Technical notes**
* Reference the existing "move project" flow — Parimal to confirm or provide examples.
* WL: feels off to me, as I commented above
* Filter the target projects project list to only those with the Documents module enabled AND where the current user has the permission to manage documents. enabled.
**Permissions and visibility considerations**
* Only visible to users who have permission to move documents in the current project project.
* The project selector should only show projects the user has access to and that have Documents enabled AND where the user has the permission to manage documents. enabled.
**Translation considerations**
* "Move to another project" — key phrase to translate in all supported languages.
**Out of scope**
* Moving multiple documents at once.
* ~~Moving Moving documents to workspaces or other top-level structures.~~
* WL: Why should we not allow moving documents to other workspaces like portfolios or programs? structures.
**I want to** move a document to a different project
**so that** I can reorganize content across projects without having to recreate it manually.
**Acceptance criteria**
* There is a "Movo
* in
* Selecting it opens a project selector dialog (reusing the existing "move project" flow where applicable).
* Only projects that have the Documents module enabled are shown in the selector.
* When a target project is selected and confirmed:
* When originally triggered from within the document:
* The document is removed from the current project and appears in the selected project. The document is reopened in the other project context.
* A success banner is shown
* When originally triggered from within the documents lists:
* The document is removed from the list
* A success banner is shown
* Reference the existing "move project" flow — Parimal to confirm or provide examples.
* Filter the target projects
**Permissions and visibility considerations**
* Only visible to users who have permission to move documents in the current project
* The project selector should only show projects the user has access to and that have Documents enabled AND where the user has the permission to manage documents.
**Translation considerations**
* "Move to another project" — key phrase to translate in all supported languages.
**Out of scope**
* Moving multiple documents at once.
* ~~Moving
* WL: Why should we not allow moving documents to other workspaces like portfolios or programs?