# Feature OP-15849 - Share work package list with users/groups/roles on project

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-15849

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 3 |
| 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 |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** a leader of some project  
**I want to** create a WP view and share it with a limited number of users  
**so that** only those users see the view, not everybody.

**Acceptance criteria**

  - WP view can be saved not only as Public or Private, but also shared with a specific set of users.

  - The target users can see the view, just as they can see their private or public views now.

Exact capabilities could range in scope, e.g.:

  - The user on the receiving end might be able to hide the view (while still having access to it, e.g. through an additional link). This could also be retrofitted for public views.

  - Sharing can be performed with user, list of users, group, list of groups and/or with all the users in some role on the project.

Ratio: Currently, one can share any filter by copy/pasting the URL, but that is cumbersome and needs to be placed somewhere out-of-band, e.g. external site/text file, etc. While the view itself doesn't provide any secret info, we may want to keep the criteria for it private to a close group, e.g. developers only.

(Requested by Evolveum, Enterprise customer. We may contribute this eventually, but likely not very soon. I'd like to hear any ideas from you as well - what could be the problems to do this, etc.)