# Feature MEET-500 - Extend work package creation modal capabilities for meeting WP outcomes

Project: Stream Meetings
Status: new
URL: https://community.openproject.org/work_packages/MEET-500

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Votes | 3 |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Meetings |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Build Number |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

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

## Estimates and progress

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

## Description

**As** a meeting user  
**I want to** be able to select in which project my WP outcome should be located  
**so that** I avoid unnecessary clicks and can make the best use out of that feature

Backstory:

When selecting 'Add existing work package' the users can search for WPs beyond the project they're currently in, it's not the case when selecting 'New work package'.  
During a team meeting, you might have a conversation for which the outcome will be purchasing train tickets or hardware and the WP would be a hardware request or a reimbursement request that don't live in the project the meeting is held in.

**Acceptance criteria**

  - TBD
    
      - Allow work package types from other projects

**Technical notes**

  - 
    <br>

**Permissions and visibility considerations**

  - *To whom is this feature visible?*

  - *When is it not visible?*

**Translation considerations**

  - *Key terms and phrases in the key languages* 

**Out of scope**

  - 
    <br>

*Set the* **To be informed/consulted teams** *field to include all teams necessary to be informed of the changes.*
