Content
View differences
Updated by Marc Alcobé almost 3 years ago
**This work package is a base for discussion. Final decisions will be recorded in the acceptance criteria.**
### Problems detected:
1. Association of the name "iCalendar" or "iCal" to Apple products.
2. Giving a full custom token name is complex for non tech users.
3. Nobody reads guideline texts bellow an input fields, therefore they don't get why they are giving a token name.
### **Acceptance criteria**
* Change the dropdown menu entry to **Subscribe to calendar**.
* Change the texts inside of the modal to:
* **Modal header:** Subscribe to calendar
* **Modal text:** You can use the URL (iCalendar) to subscribe to this calendar in an external client and view up-to-date work package information from there.
* **Form field label:** Where will you be using this?
* **Form placeholder:** Type a name, e.g. “Phone”
* **Form guideline text:** If you subscribe subscribed to this calendar from multiple devices, this name will help you distinguish between them in your [access tokens](https://community.openproject.org/my/access_token) list.
* The **toast text** also changes to: The URL “\[User input\]” was successfully copied to your clipboard. Paste it in your calendar client to complete the subscription.
* Keep the current logic of not being able to have two tokens with the same name.
## Visuals
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/64031/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/64062/content"><img src="/api/v3/attachments/64032/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/64063/content"><img src="/api/v3/attachments/64035/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/64033/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/64036/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/64034/content">
## Figma
https://www.figma.com/file/0XYbNtiBhnGWYHtzmynWI8/iCalendar-subscription?type=design&node-id=0-1&mode=design
### Problems detected:
1. Association of the name "iCalendar" or "iCal" to Apple products.
2. Giving a full custom token name is complex for non tech users.
3. Nobody reads guideline texts bellow an input fields, therefore they don't get why they are giving a token name.
### **Acceptance criteria**
* Change the dropdown menu entry to **Subscribe to calendar**.
* Change the texts inside of the modal to:
* **Modal header:** Subscribe to calendar
* **Modal text:** You can use the URL (iCalendar) to subscribe to this calendar in an external client and view up-to-date work package information from there.
* **Form field label:** Where will you be using this?
* **Form placeholder:** Type a name, e.g. “Phone”
* **Form guideline text:** If you subscribe
* The **toast text** also changes to: The URL “\[User input\]” was successfully copied to your clipboard. Paste it in your calendar client to complete the subscription.
* Keep the current logic of not being able to have two tokens with the same name.
## Visuals
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/64031/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/64062/content"><img
## Figma
https://www.figma.com/file/0XYbNtiBhnGWYHtzmynWI8/iCalendar-subscription?type=design&node-id=0-1&mode=design