Content
View differences
Updated by Oleksii Borysenko 2 days ago
**As** an app user\
\
user
**I want to** open the meeting link from description and comments in the app\
\
app
**so that** so that I can read/edit/delete meetings meetings
### Acceptance Criteria
* When a user taps a **meeting link** shown from a work package context (e.g., linked on the work package), the meeting opens **inside the app** (in an in-app view), not in an external browser.
* When a user taps a **work package link** shown from a meeting context (e.g., work package referenced/linked in meeting notes/details), the work package opens **inside the app**, not in an external browser.
* This applies wherever these links appear in the app, including:
* Work package details view (any “Meetings”/linked content section)
* Meeting detail view / meeting notes view (any “Related work packages”/linked items section)
* Activity feeds / comments where such links are rendered
* Links that point to **internal OpenProject entities** (work packages, meetings) are recognized as internal deep links and routed in-app.
* If the app cannot resolve a link as an internal entity (unknown URL, unsupported type), it may fall back to external browser behavior.
* If the user does not have permission to view the target entity:
* The app does not open an external browser as a workaround
* The app shows an in-app error state (e.g., “You don’t have access” / “Not found”)
### Technical Notes
*
<br>
### Permissions and Visibility Considerations
*
<br>
### Translation Considerations
*
<br>
### Out of Scope
* Redesigning the meeting/work package UI, only link opening behavior is in scope.
* Implementing universal links/app links at the OS level.
<br>

<figure class="image image_resized op-uc-figure" style="width:290px;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/924130/content"></div></figure>
<br>
\
\
### Acceptance Criteria
*
*
*
*
*
<br>

<br>