-
Suggestion
-
Resolution: Unresolved
-
432
-
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 Failed to load
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
Form Name |
---|
Just wondering what the outcome of this discussion was, or is it still ongoing? The team must be getting a bit hungry by now, maybe time for a lunch break and time-boxing the followup session to force a decision before they reach retirement age and you have to start the discussion all over again with the new joiners?
This is very much a functional bug that was missed when the solution design for dependent fields was being discussed. It really should be addressed sooner rather than later. Adding new, shiny features is cool, but not as cool as having a product that works the way your customers expect it to work.