Content
View differences
Updated by Parimal Satyal almost 4 years ago
## **Acceptance criteria**
* The current browser modal is substituted with this implementation.
* The modal is composed with this elements in order from top to down:
* Header: with a title in this case "Remove file link" / "Delete attachment".
* Divider: full width.
* Content of the modal: in this case a simple text:
* For removing links: remove link: "Are you sure you want to unlink this file from this work package? Unliking does not affect the original file and only removes the connection to this work package."
* For deleting attachments: "Are you sure you want to delete this file? This action is not reversible."
* It might change depending of the modal (eg. cards on boards, text fields in backup codes...).
* Action bar with always two actions:
* "Cancel" button to cancel the process.
* Action button in this case "Remove link" / "Delete attachment" (it might change the style of the button if the action is destructive or not).
* This modal will be added to the design system.
* The alert modal when a work package is deleted will follow this implementation to keep things coherent.
* Other modals that are blocking the complete screen UI will also follow this implementation to maintain coherence:
* Invite user
* Delete work package
* Work package table settings
* Add widget
* New board (type)
* Help > Introduction video
* My account > Two-factor authentication > Backup codes password
## Out of scope
* Substitute all the other browser modals until it has been analysed the impact and places where this happens.
* Substitute other modals that are still not happening on a modal state (ruby on rails implementation delete user from admin settings).
## Visual
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/37178/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/37179/content">
## Figma
https://www.figma.com/file/gtLQfPe09X7XugAH8L7dTy/Nextcloud-Integration?node-id=2307%3A66252
* The current browser modal is substituted with this implementation.
* The modal is composed with this elements in order from top to down:
* Header: with a title in this case "Remove file link" / "Delete attachment".
* Divider: full width.
* Content of the modal: in this case a simple text:
* For removing links:
* For deleting attachments: "Are you sure you want to delete this file? This action is not reversible."
* It might change depending of the modal (eg. cards on boards, text fields in backup codes...).
* Action bar with always two actions:
* "Cancel" button to cancel the process.
* Action button in this case "Remove link" / "Delete attachment" (it might change the style of the button if the action is destructive or not).
* This modal will be added to the design system.
* The alert modal when a work package is deleted will follow this implementation to keep things coherent.
* Other modals that are blocking the complete screen UI will also follow this implementation to maintain coherence:
* Invite user
* Delete work package
* Work package table settings
* Add widget
* New board (type)
* Help > Introduction video
* My account > Two-factor authentication > Backup codes password
## Out of scope
* Substitute all the other browser modals until it has been analysed the impact and places where this happens.
* Substitute other modals that are still not happening on a modal state (ruby on rails implementation delete user from admin settings).
## Visual
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/37178/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/37179/content">
## Figma
https://www.figma.com/file/gtLQfPe09X7XugAH8L7dTy/Nextcloud-Integration?node-id=2307%3A66252