# Feature OP-7466 - Hidden data to work package

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

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

**Context**

We are trying to integrate OpenProject into our company processes (not only developing but all business processes). We are planning to heavylly use webhooks. During webhooks we want to store additional data into work\_package like other DB's identificators, statuses and so on. By now I see only one way to do this. Create custom text field and store custom JSON into it. But as you can imagine this way has UI disadvantage.Users will see all that technical data. 

The other way is to create helper database to save all metadata. This way has disadvantages too. It increases system's compexity/

**Suggestion**

I suggest to create hidden custom field 'additional' which will be available only on webhooks and API calls and will not be visible to users. This field contains any custom JSON data.
