# Feature OP-14525 - Allow setting createdAt, author via API

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-14525

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 14.0.0 |
| Sprint | 14.0.0 |
| 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 |  |
| 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** someone wanting to migrate data to OpenProject  
**I want to** be able to set the createdAt properties when creating work packages (and other records, where applicable) via the API  
**so that** I can preserve information from my source system.

**Acceptance criteria**

*   As an admin user and createdAt properties can be set in POST requests, allowing for dates in the past
    *   For now, this is possible for projects and work packages

Note: The current implementation feels like a severe constraint in migrating information from other systems to OpenProject via the API. While I can understand the underlying assumption, it does hold for the use case of migrating a large number of records in one batch, IMHO. I would definitely limit this to request creating a record for the first time.
