Content
View differences
Updated by Klaus Zanders about 20 hours ago
Currently in OpenProject, custom fields can be assigned to projects and work package types, but their available options and default values are shared globally across all types. This creates friction for teams that need different option sets depending on project and/or work package type. Within Jira Data Center custom field contexts can be scoped to specific issue types and/or projects.
Examples:
* The field customer might have different set of options in each project.
* A priority field might default to _Medium_ for Tasks but _High_ for Bugs.
Main goals:
* Allow administrators to define default values per custom field per work package type and/or project.
* Allow administrators to restrict available options per custom field per work package type and/or project.
* Allow administrators to mark items as inactive. The work packages that still have that value retain it, but you cannot select it as an option for new work packages.
Examples:
* The field customer might have different set of options in each project.
* A priority field might default to _Medium_ for Tasks but _High_ for Bugs.
Main goals:
* Allow administrators to define default values per custom field per work package type and/or project.
* Allow administrators to restrict available options per custom field per work package type and/or project.
* Allow administrators to mark items as inactive. The work packages that still have that value retain it, but you cannot select it as an option for new work packages.