Details
-
Bug
-
Status: Done
-
Low
-
Resolution: Fixed
-
6.40.0
-
SR4J Sprint 113, SR4J Sprint 114, SR4J Sprint 115
-
2.1
Description
Summary
The server-side behaviour script of a field that’s not present on the issue operation screen is still being executed.
Steps to Reproduce the Problem
- Remove the Description field from the test project's Create Issue Screen
- Create a Server-Side Behaviour for the Description field and add the following script:
getFieldById("summary").setFormValue("Description field is not on this screen.")
- Click on the Create button on the top navigation bar to bring up the Create Issue dialogue.
Note that there is no value in the Summary field.
- Now, create an Initialiser and add the script below:
getFieldById("description").setFormValue("Initialiser script")
- Click on the Create button to bring up the Create Issue dialogue.
Note the value in the Summary field.
Expected Behaviour
The Summary field's form value set in the Description field's Server-Side script should not be triggered unless the Description field is present on the screen.
Actual Behaviour
The Summary field's form value set in the Description field's Server-Side Behaviour is populated although the Description field is not on the screen.
Additional Info
- Reproduced in Jira Software 8.13.9 | ScriptRunner 6.37.0, 6.40.0.
- SRJSUP-22423 Demo.mov
Attachments
Issue Links
- relates to
-
SRJIRA-5296 Even if the Field is not added to the Screen, the Field's Server-Side Behaviour is still able to work
-
- Done
-