# Epic OP-14151 - Allow embedded tables to be evaluated in a (different) project context

Project: OpenProject
Status: rejected
URL: https://community.openproject.org/work_packages/OP-14151

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

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

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Designer |  |
| Developers |  |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

**As** a user of multiple projects  
**I want to** include some filtered view specific to one project in an embedded table  
**so that** create a report on what is relevant for this one project

Currently, am embedded table is always evaluated in the current context

*   Global, in case of the My Page
    
*   Current project, in case of the project dashboard, or embedded table macro
    

This results in being unable to filter for values that are not defined in the current project, even if the other project is included using the &quot;projects include&quot; functioality:

*   Types
    
*   Versions (if not shared globally)
    
*   Custom fields
    

**Acceptance criteria**

*   Provide a UI element to the configuration modal to select in which project the embedded table will be evaluated in
