-
Type:
Bug
-
Status: Done (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 6.6.0
-
Fix Version/s: 6.12.0
-
Component/s: Behaviours
-
Labels:None
-
Sprint:SR4J Sprint 87
-
Critical Points:3.9
Steps to Reproduce
Test 1
- Add a Database Picker field to your project
- Configure the SQL Queries for the Database Picker field and save it. The image below displays an example Database Picker configuration:-
- Next, create a new Behaviour for the Service Desk. Use the Initialiser to set the Behaviour.
Below is the sample behaviour code:-def apps = getFieldById("customfield_11701") apps.setDescription("Testing 123") apps.setFormValue(["Design"])
And below is a print screen of the sample behaviour configuration:-
- Next, go to the Service Desk and try to create a ticket.
Test 2
- Add a Database Picker field to your project
- Configure the SQL Queries for the Database Picker field and save it. The image below displays an example Database Picker configuration:-
- Next, create a new Behaviour for the Service Desk. Use the Initialiser to set the Behaviour.
Below is the sample behaviour code:-def apps = getFieldById("customfield_11701") apps.setDescription("Testing 123") apps.setFormValue("1")
And below is a print screen of the sample behaviour configuration:-
- Next, go to the Service Desk and try to create a ticket.
Current Behaviour
At the moment, the default form value configured in the Behaviour doesn't get passed to the Database Picker field.
Below is a print screen of the web browser's console output:-
Although the browser's console displays the default value, the Database Picker fails to do so.
Expected Behaviour
The Behaviour should be able to set the form value for the Database Picker field according to the Behaviour configuration.
Additional Information
Test video included test1.mp4