Content
View differences
Updated by Marc Alcobé 8 months ago
**As** a user
**I want to** provide user to the OpenProject team feedback
**so that** they can fix bugs and implement new features
**Acceptance criteria**
* [ ] There are two new entries inside the user settings page inside the section `Feedback`:
* [ ] `Rate the app`: open directly open the OS store (Apple Store or Google Play) to rate the app.
* [ ] `Give feedback`: open a full form modal based on the work package creation form that allow the user to report feedback. This contains the following information:
* [ ] Subject:
* [ ] This will be used as the work package subject.
* [ ] Description:
* [ ] This will be used as the work package description.
* [ ] Attach a file in an `Attachments` section:
* [ ] The file that will be attached to the work package created.
* [ ] Feedback type inside a `Details` section:
* [ ] This will define the work package type inside the mobile app feedback project: Feedback, Bug or Feature.
* [ ] Version (non-editable and filled automatically) inside a `Details` section:
* [ ] This should be added directly in the field “Found “Bug found in mobile version”. version” in the case of bugs.
* [ ] For Feedback and Feature should be added to the description as text.
* [ ] When the user submits the feedback, then this is transmitted to OpenProject Community and transformed into a work package with all the relevant information.
**Technical notes**
* [ ] We will proceed with storing the API key inside the mobile app locally as a temporal solution until <mention class="mention" data-id="67433" data-type="work_package" data-text="###67433">###67433</mention> is clarified.
* [ ] A dedicated mobile feedback user and project on community needs to be created.
* [ ] Create a temporary api-token called “intermediate mobile feedback token”
**Figma and visuals**
<br>
**Out of scope**
* [ ] The authentication is completed and double proved as the discussion on the web app is still under discussion.
**I want to** provide user to the OpenProject team feedback
**so that** they can fix bugs and implement new features
**Acceptance criteria**
* [ ] There are two new entries inside the user settings page inside the section `Feedback`:
* [ ] `Rate the app`: open directly open the OS store (Apple Store or Google Play) to rate the app.
* [ ] `Give feedback`: open a full form modal based on the work package creation form that allow the user to report feedback. This contains the following information:
* [ ] Subject:
* [ ] This will be used as the work package subject.
* [ ] Description:
* [ ] This will be used as the work package description.
* [ ] Attach a file in an `Attachments` section:
* [ ] The file that will be attached to the work package created.
* [ ] Feedback type inside a `Details` section:
* [ ] This will define the work package type inside the mobile app feedback project: Feedback, Bug or Feature.
* [ ] Version (non-editable and filled automatically) inside a `Details` section:
* [ ] This should be added directly in the field “Found
* [ ] For Feedback and Feature should be added to the description as text.
* [ ] When the user submits the feedback, then this is transmitted to OpenProject Community and transformed into a work package with all the relevant information.
**Technical notes**
* [ ] We will proceed with storing the API key inside the mobile app locally as a temporal solution until <mention class="mention" data-id="67433" data-type="work_package" data-text="###67433">###67433</mention> is clarified.
* [ ] A dedicated mobile feedback user and project on community needs to be created.
* [ ] Create a temporary api-token called “intermediate mobile feedback token”
**Figma and visuals**
<br>
**Out of scope**
* [ ] The authentication is completed and double proved as the discussion on the web app is still under discussion.