-
Suggestion
-
Resolution: Unresolved
-
614
-
11
-
Issue Summary
When using cascading fields(using Filter issue scope), the dependent field value doesn’t get removed automatically when the master field value is changed. This will lead to incorrect data in Jira issue.
Steps to Reproduce
- Create 2 Insight object custom fields: Country and City
- Master field: Country and Dependent field: City
- For Country value Italy, the City values are Venice, Rome
- For Country value Germany, the City values are Berlin, Bonn
- In Country field select Italy and in dependent field City set Rome.
- Change the Country to Germany but the City field still shows Rome unless manually changed.
- In this case if the City value is not changed and you continue with ticket creation, the Jira issue will end up with wrong data. Country: Germany ; City: Rome
Expected Results
The depended field City should be cleared out automatically as soon as the master field Country is changed.
Actual Results
The dependent field value does not get cleared automatically.
Workarounds
Once the master field value is changed, click on the small cross icon in dependent field to clear the existing data. Type some letters of the dependent value which will show the value in dropdown menu, then select to set it.
- duplicates
-
JSDCLOUD-11706 Auto-suggestions on Insight objects custom fields are sometimes showing incorrect options
- Closed
-
JSDCLOUD-10310 Clear Insight field value when the value of a custom field used in the filter scope updates
- Under Consideration
- derives
-
JDW-4019 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...