System fields in Jira are not behaving as expected
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
System fields in Jira are not behaving as expected. This can be applied to Affect Version/s, Fix Version/s, Components, or any other system field.
One example of unexpected behavior: Existing values are removed when attempting to edit the field (either the 'Edit' button or inline edit).
Environment
Any version of Jira
Diagnosis
There may be many types of unexpected behaviours these fields are facing. Here are some of the known behaviours
Existing values are removed when attempting to edit the field (either 'Edit' button or inline edit)
Jira VM template files have been modified
This can be confirmed by searching for the string 'Modified Files' in the latest startup logs
1 2 3 4___ Modifications ___________________________ Modified Files : templates/jira/issue/field/components-edit.vm, templates/jira/issue/field/versions-edit.vm
Cause
These templates controls the behaviour of the system fields in Jira. By modifying these templates, the behaviour of the fields will be affected. The unexpected behaviour is either what the modification is meant to achieve, or an unwanted side effect of the modification.
Solution
Revert all modifications done to these VM template files
Restart Jira for the changes to take effect
Was this helpful?