# Feature OP-11814 - Erweiterte Ausgabe von Informationen - Platzhalterbenutzer

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

## 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 |  |
| 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

**As,** Admin and Project Admin

How did we come to OpenProjekt? Through the connection to Nextcloud. We use Nextcloud intensively for data exchange and in the area of mobile working. The connection to OpenProjekt allows us to provide documents in schedules or to documentation requirements. The possibility to map information about all projects is convincing.

**Description of the working method**  
We use OP in the field of architecture. Our special requirements lie in the documentation and monitoring of internal and external processes.

* Internal: Planning or documentation
* External: Construction execution or defect removal.

Between the external and internal processes there are many dependencies to external persons, clients or companies (placeholder users).

* These can all be mapped via tasks, dates and deadlines and via subsequent assignments, short information is given to the types via the descriptions and &quot;travels through the project&quot;
* After the definition of a task over work packages or over boards and the assignment to users or placeholder users these are to be supervised
* There will be a lot of placeholder users

In order to clarify the way we work, I have attached the screen shots 1-3.   
The user-defined fields we have created are shown in Appendix 5. The field in the format &quot;long text&quot; is also used to insert cell phone photos into the documentation.

So far, all of this is very easy to organize in OP and to assign to topics via the filters. Many thanks for the work done.

**I want to**

1. grouping of information for documentation purposes  
    Solution 1 about the work packages is basically possible but the descriptions cannot be included. In case of the construction diary (consists of the types &quot;Weather data&quot; and &quot;Construction diary&quot;) it becomes too many columns even without descriptions.
2. grouping the information on the meetings module.   
    Two work package tables are included, the number of columns remains manageable and grouping on a period is Simple. For the next period, the meeting &quot;construction diary&quot; is copied and the period is adjusted.

**so that** _\[enter desired result\]_

Gladly would like to proceed as mentioned under second. For this it is necessary to be able to output the descriptions and the field type &quot;Long text&quot;.  
Gladly in a second line under the other columns.

I would like to make a second request: if it is then possible to send documents to the placeholder users, it will be really nice.

**Acceptance criteria**

* According to my estimation this function extension is interesting for many users. The usage scenario we have shown is a common one.
* For the architecture area, a considerable amount of currently redundant information can be eliminated.
* We can finally delegate routine tasks easily and have them done in the office across all projects by a secretary.
