Content
View differences
Updated by Marc Alcobé about 1 month ago
As a **platform user**
I want to **long-tap on text or images within Work Package descriptions and Activities to access native OS options**
so that **I can easily copy, translate, share, or otherwise reuse content using familiar system tools**
**Acceptance criteria**
* Users can perform a **long tap (tap-and-hold)** on text within Work Package descriptions and Activities
* Upon long tap on text:
* Native OS text selection handles appear
* Native OS context menu is displayed (e.g. Copy, Translate, Share, Copy Link with Highlight on iOS)
* Users can adjust the selection range using OS-native controls
* Selected text can be copied and pasted outside the app
* When long tapping on images:
* Native OS image interaction menu is displayed (e.g. Copy, Share, Save Image where supported)
* Behavior is consistent with platform conventions:
* iOS uses native selection and context menu
* Android uses native text selection toolbar and image actions
* Feature works across:
* Work Package descriptions
* Activity descriptions
* Long texts custom fields
* No custom in-app overlay replaces or conflicts with native OS menus
* Feature does not interfere with scrolling or other gestures
**Technical notes**
* Use **native OS components** for text selection and context menus (no custom implementation unless required)
* Ensure text is rendered in a **selectable format**
* For images:
* Enable long-press gesture recognisers tied to OS-level actions
* Avoid gesture conflicts with:
* Scroll views
* Expand/collapse interactions
* Ensure compatibility with:
* iOS text interaction APIs (e.g. `UITextView` / `UIContextMenuInteraction`)
* Android text selection framework (`TextView` selectable, `ActionMode`)
**Permissions and visibility considerations**
_**To whom is this feature visible?**_
* All users who can view Work Package descriptions and Activities
_**When is it not visible?**_
* When content is restricted due to permissions (e.g. no access to the Work Package or Activity)
* When text/images are rendered in non-selectable formats (e.g. legacy components, unsupported content types)
* In read-only environments where OS-level interaction is explicitly disabled
**Translation considerations**
* All labels are **managed by the OS**, so no manual translation is required
**Out of scope**
* Custom context menus replacing native OS options
* Annotation or commenting via text selection
* Advanced image editing features
* Cross-app deep integrations beyond OS-provided capabilities
I want to **long-tap on text or images within Work Package descriptions and Activities to access native OS options**
so that **I can easily copy, translate, share, or otherwise reuse content using familiar system tools**
**Acceptance criteria**
* Users can perform a **long tap (tap-and-hold)** on text within Work Package descriptions and Activities
* Upon long tap on text:
* Native OS text selection handles appear
* Native OS context menu is displayed (e.g. Copy, Translate, Share, Copy Link with Highlight on iOS)
* Users can adjust the selection range using OS-native controls
* Selected text can be copied and pasted outside the app
* When long tapping on images:
* Native OS image interaction menu is displayed (e.g. Copy, Share, Save Image where supported)
* Behavior is consistent with platform conventions:
* iOS uses native selection and context menu
* Android uses native text selection toolbar and image actions
* Feature works across:
* Work Package descriptions
* Activity descriptions
* Long texts custom fields
* No custom in-app overlay replaces or conflicts with native OS menus
* Feature does not interfere with scrolling or other gestures
**Technical notes**
* Use **native OS components** for text selection and context menus (no custom implementation unless required)
* Ensure text is rendered in a **selectable format**
* For images:
* Enable long-press gesture recognisers tied to OS-level actions
* Avoid gesture conflicts with:
* Scroll views
* Expand/collapse interactions
* Ensure compatibility with:
* iOS text interaction APIs (e.g. `UITextView` / `UIContextMenuInteraction`)
* Android text selection framework (`TextView` selectable, `ActionMode`)
**Permissions and visibility considerations**
_**To whom is this feature visible?**_
* All users who can view Work Package descriptions and Activities
_**When is it not visible?**_
* When content is restricted due to permissions (e.g. no access to the Work Package or Activity)
* When text/images are rendered in non-selectable formats (e.g. legacy components, unsupported content types)
* In read-only environments where OS-level interaction is explicitly disabled
**Translation considerations**
* All labels are **managed by the OS**, so no manual translation is required
**Out of scope**
* Custom context menus replacing native OS options
* Annotation or commenting via text selection
* Advanced image editing features
* Cross-app deep integrations beyond OS-provided capabilities