Actions
Feature #44421
openPrevent unintended updates to required custom fields added after issue creation
Status:
New
Priority:
Normal
Assignee:
-
Category:
Custom fields
Target version:
-
Resolution:
Description
This proposal concerns custom fields that are added after an issue has been created.
When editing an issue, a newly added custom field is normally left empty, which is natural for fields such as text fields.
However, for a required custom field that uses a dropdown list, the default value is not selected, making it appear as though a value has already been set. As a result, an unintended value may be saved unless the user explicitly changes it.
The two custom field formats that support both dropdown selection and a default value are List and Boolean.
This patch selects the default value when all of the following conditions are met:
- The field uses a dropdown list.
- The field is required.
- A default value is configured.
Files
No data to display
Actions