Component and/or Affected Version field values are removed upon issue transition post Jira upgrade
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
After upgrading from version 8.20.x to 9.4.x, Component and/or Affected Version field values are removed after making a transition in Jira.
There is no workflow post function configured that would do this.
Environment
9.x.x
Diagnosis
Since this has happened right after the upgrade, the included customizations need to be checked against the list of files printed in atlassian-jira.log upon startup. Due to the major upgrade and several potential changes/fixes, it is possible that the custom script may not be compatible with the 9.x release and, thus, needs to be reviewed and rectified accordingly.
1
2
3
Modified Files : WEB-INF/web.xml, templates/email/subject/issueworklogupdated.vm, templates/email/subject/issuecommentedited.vm, seraph-config.xml, logging.properties, templates/email/subject/issuecreated.vm, templates/email/subject/issueresolved.vm, templates/email/subject/issuedeleted.vm, templates/email/subject/issueworkstarted.vm, templates/email/subject/issuenotify.vm, jira-application.properties, templates/email/subject/issuecommented.vm, templates/email/subject/issueassigned.vm, templates/email/subject/issueworklogged.vm, outlook-email.translations, templates/email/subject/issuereopened.vm, templates/email/subject/issueupdated.vm, templates/email/subject/issuementioned.vm, templates/email/subject/issueworkstopped.vm, templates/email/subject/issueworklogdeleted.vm, templates/email/subject/issueclosed.vm, templates/email/subject/issuemoved.vm
Removed Files : templates/plugins/jira/issuetabpanels/changehistory.vm, templates/email/html/includes/header.vm, secure/admin/user/views/userbrowser.jsp, velocity.properties, templates/email/subject/issuegenericevent.vm Cause
Specific customizations have been made which are causing this behaviour. Example customized files that are causing this behaviour:
atlassian-jira/WEB-INF/classes/templates/plugins/jira/issuetabpanels/changehistory.vm
atlassian-jira/WEB-INF/classes/templates/plugins/jira/issuetabpanels/changehistory_macros.vm
atlassian-jira/WEB-INF/classes/templates/jira/issue/field/components-edit.vm
atlassian-jira/WEB-INF/classes/templates/jira/issue/field/versions-edit.vm
atlassian-jira/WEB-INF/classes/templates/plugins/fields/edit/edit-datepicker.vm
atlassian-jira/WEB-INF/classes/templates/plugins/fields/edit/edit-multiuser.vm
atlassian-jira/WEB-INF/classes/templates/plugins/fields/edit/edit-userpicker.vm
Please note: there could be other files that have been modified and contribute to this behaviour. Since all customization are environment-specific, Atlassian is not aware of all the changes done on user environment that could be contributing to the issue. Customizations like this one go beyond our support scope and we can only provide advice on a best-effort basis.
Solution
Either of the steps could be taken to address the issue.
Rectify the customisations to make it compatible with 9.x.x
OR
Replace it with the default files from 9.x.x.
Take a backup of all the modified files
Download and extract the default ones from downloading Jira archive
Locate the original (stock) files from the extracted archive. For example,
changehistory.vmunder /Downloads/atlassian-jira-software-9.x.x-standalone/atlassian-jira/WEB-INF/classes/templates/plugins/jira/issuetabpanelsReplace modified files with the original (stock) ones from the extracted archive.
Restart Jira
Was this helpful?