Content
View differences
Updated by Jens Ulferts about 9 hours ago
**As** an admin
**I would like** to quickly and programmatically populate and update the available options of custom fields of type ~~List,~~ Hierarchy, and Weighted item list via API
**so that** I can have a different system managing those options.
**Note:** List custom fields are excluded as they are migrated to hierarchy fields.
Example:
An HR management system holds the information of a company's organizational structure and wants to mirror that structure into OpenProject so that it can be used for filtering work packages, projects and users.
**Acceptance criteria:**
* Hierarchy and weighted list item custom fields have an API for adding and updating values
* List custom fields are migrated to hierarchy fields.
* This requires time entries, versions, user and groups to allow having hierarchy fields.
* "Hierarchy" is renamed to "Simple list"
* "Weighted item list" is renamed to "Weighted list"
* Make the feature to create customs fields of type hierarchy a CE feature
**I would like** to quickly and programmatically populate and update the available options of custom fields of type ~~List,~~ Hierarchy, and Weighted item list via API
**so that** I can have a different system managing those options.
**Note:** List custom fields are excluded as they are migrated to hierarchy fields.
Example:
An HR management system holds the information of a company's organizational structure and wants to mirror that structure into OpenProject so that it can be used for filtering work packages, projects and users.
**Acceptance criteria:**
* Hierarchy and weighted list item custom fields have an API for adding and updating values
* List custom fields are migrated to hierarchy fields.
* This requires time entries, versions, user and groups to allow having hierarchy fields.
* "Weighted item list" is renamed to "Weighted list"
* Make the feature to create customs fields of type hierarchy a CE feature