Fields value getting wiped out unexpectedly while updating issue via Edit screen. A bug in Jira DC?

Question

We are running Jira Data Center v11.3.8. Users have been reporting a strange issue. The issue is while updating a custom field (for example, Field A) via Edit screen, other custom fields on the same screen (such as Field B, Field C, etc.) that already contained values are sometimes cleared after submitting the form, even though the user did not modify them. The issue is intermittent and has only been observed in our production environment, making it difficult to reproduce consistently in Dev environment.

Noteworthy to mention that we upgraded to Jira v11.3.8 a few months ago, and these complaints started appearing after the upgrade. However, we cannot confirm whether the issue is related to upgrade.

Also, note that we heavily use Script Runner behavior to implement custom need on the screens. However, there is no logic in the Behavior scripts that is to wipe out fields or clearing fields.

So, wanted to reach out here to see if anyone else in the community experienced similar behavior? If yes, what was the work around that you took to remedy this annoying issue?

~ Alauddin Azad

Viswanathan Ramachandran · Answer

To echo Joseph below, contact Adaptavist support.

You might need to add/set com.onresolve.jira.groovy.user.FieldBehaviours parameter to debug and reproduce the issue to see the logs.

As to quickly test, try disabling behaviours and see how it behaves. You need to drill down issues slowly as which behaviours causing this.

Joseph Chung Yin · Answer

@Alauddin Azad

This is was the case, I recommend you to reach out to Adaptavist (vendor of the ScriptRunner for Jira add-on) directly and provide your details.  What they will ask you to do is to generate support.zip after you enable profile/logging of the add-on, then repo the issue and generate the support zip.  They will also ask for your behavior script configuration too.

In general, action on one field should not whip out other fields values automatically.

Last thing, have you also check to see if there are any Automation Rules for Jira rules defined based on "field  value changed" triggering event in your envs where it contain actions to edit those other fields values.

Hope this also helps.

Best, Joseph

Alauddin Azad · Answer

Hi @Viswanathan Ramachandran thanks for your inquiries. Please see my response below inline with your query - Do you have Scriptrunner installed with any behaviours set? and the add-on is also upgraded? Yes, the plugin Adaptavist ScriptRunner for JIRA was also upgraded to 10.14.0 while upgarding Jira software to 11.3.8 Does it happen on all the projects? AA: Yes Have you tested on a simple project with no customisations? AA: No, cause it is happening in Prod env and we couldn't reproduce it in LLE which makes debugging very challenging. What does the logs say? AA: Analyzing atlassian-jira.log did not yield any clue meaning no unhandled error/exception occurring. Thanks.