Content
View differences
Updated by Marc Alcobé 3 months ago
**User story 1**
**As** a QA manager
**I want to** share pictures from a screenshot
**so that** I don't have to manually select the file in the work package create form.
**User story 2**
**As** a facility manager
**I want to** share pictures from the iOS gallery with the OpenProject mobile app
**so that** I can create a task or file a defect directly from a picture without switching to the app first.
**Acceptance criteria**
* [ ] When clicking the share action from the photos or files OS apps, there is an option “OpenProject” similar to “WhatsApp”.
* [ ] The user must be logged in into an instance to share the element as an attachment into a work package.
* [ ] If the user is not logged in, the first screen displayed is the login. Once logged in, the share form is opened.
* [ ] The share form states which documents are being shared as attachments and allow the user to select which action wants to take:
* [ ] Create a new work package
* [ ] Attach to existing work package
* [ ] Only work packages where the user have permissions can attach files shouls be displayed on the search results of the bottom sheet.
* [ ] If the user choses to create a new work package, a section with the mandatory information for the work package creation `Project` and `Type` can be filled.
* [ ] Once the user fills the information can continue to the normal work package creation form and the files will be added in the files tab as attachments once the flow is completed. The flow ends with the work package opened.
* [ ] Only projects where the user have permissions to attach files should appear as option.
* [ ] The app remembers the type and the project for the next work package as a pre-selection.
* [ ] If the user choses to attach the files to an existing work package, the user can proceed through the `Continue` button and a search work package list view will be open to search the desired work package.
* [ ] With a single tab, the user can select the work package to attach the files, that should open the work package in the `Files tab` and the tooltip confirming the attachment should be displayed.
**Technical notes**
* <br>
**Permissions and visibility considerations**
* We need to know the user permissions for `creating work packages` and `attach files`.
* Users who doesn't have permissions to attach files will see an error screen after login in.
* Users who can't create work packages in the instance at all will see the action to create grey out, and they can only attach to existing files.
* Only work packages where the user have permissions can attach files shouls be displayed on the search results of the bottom sheet.
**Translation considerations**
* New strings are added to this flow and will need to be reviewed
**Out of scope**
* <br>
**As** a QA manager
**I want to** share pictures from a screenshot
**so that** I don't have to manually select the file in the work package create form.
**User story 2**
**As** a facility manager
**I want to** share pictures from the iOS gallery with the OpenProject mobile app
**so that** I can create a task or file a defect directly from a picture without switching to the app first.
**Acceptance criteria**
* [ ] When clicking the share action from the photos or files OS apps, there is an option “OpenProject” similar to “WhatsApp”.
* [ ] The user must be logged in into an instance to share the element as an attachment into a work package.
* [ ] If the user is not logged in, the first screen displayed is the login. Once logged in, the share form is opened.
* [ ] The share form states which documents are being shared as attachments and allow the user to select which action wants to take:
* [ ] Create a new work package
* [ ] Attach to existing work package
* [ ] Only work packages where the user have permissions can attach files shouls be displayed on the search results of the bottom sheet.
* [ ] If the user choses to create a new work package, a section with the mandatory information for the work package creation `Project` and `Type` can be filled.
* [ ] Once the user fills the information can continue to the normal work package creation form and the files will be added in the files tab as attachments once the flow is completed. The flow ends with the work package opened.
* [ ] Only projects where the user have permissions to attach files should appear as option.
* [ ] The app remembers the type and the project for the next work package as a pre-selection.
* [ ] If the user choses to attach the files to an existing work package, the user can proceed through the `Continue` button and a search work package list view will be open to search the desired work package.
* [ ] With a single tab, the user can select the work package to attach the files, that should open the work package in the `Files tab` and the tooltip confirming the attachment should be displayed.
**Technical notes**
* <br>
**Permissions and visibility considerations**
* We need to know the user permissions for `creating work packages` and `attach files`.
* Users who doesn't have permissions to attach files will see an error screen after login in.
* Users who can't create work packages in the instance at all will see the action to create grey out, and they can only attach to existing files.
* Only work packages where the user have permissions can attach files shouls be displayed on the search results of the bottom sheet.
**Translation considerations**
* New strings are added to this flow and will need to be reviewed
**Out of scope**
* <br>