# Feature OP-13198 - In full-screen view, always open work packages in their own project

Project: OpenProject
Status: in specification
URL: https://community.openproject.org/work_packages/OP-13198

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Parimal Satyal |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

### **Context**

Today, work packages can be accessed in two main contexts: *out-of-project* or *in-project.*

A good example of out of project is when you view a work package in split screen view via Notifications or the Team Planner; the contents are accessed from a page that does not live under or belong to any project. To get around this issue, a blue box currently indicates parent project, as specified in <mention class="mention" data-id="44340" data-type="work_package" data-text="###44340">###44340</mention>.

### The Problem

The out-of-project scenario is inherent to split-screen views, since they they can display transversal or cross-project content. However, currently, when a user opens a work package in 'full-screen' view from Notifications for example by clicking on the full-screen icon or the work package id link, the work package is *still* displayed out of context. In other words, the URL does not include the project ID and the blue box is still displayed.

The full screen view, dispite not being a modal or an overlay, does not point to the canonical in-project URL of the work package.

Users have complained that finding this in-project URL is difficult and wondered why the work package doesn't simply open in-project to begin with.

### **Acceptance criteria**

  - When opening a work package in full-screen view (that is, when redirecting to it completely, not as an overlay, split-screen or a modal):
      - Point to its canonical in-project URL
      - Do not show the blue box indicating project

### **Screen capture**

**How it currently is:**

**<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/68365/content">**
