-
Suggestion
-
Resolution: Unresolved
-
367
-
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
-
-
- Under Consideration
- derives
-
JDW-4019 Failed to load
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDCLOUD-10496] When using Assets object cascading fields, the dependent field value doesn’t get removed automatically when the master field value is changed
Happy New Year, everyone! May it be filled with joy, success, and - who knows - maybe even some miracles. Like Atlassian resolving to fix this bug. We can dream, right?
I think this issue type should be a Bug.
When the master field is changed, the other connected field does not change and if the create button is clicked, it creates an issue.
I think this is a bug and needs to be fixed.
We cannot use the Select List Cascading field type in the Form and build conditionals because it is not compatible with JSDCLOUD-10792
We can use Assets fields and simulate a "Cascading" effect in the Form, but the value of the dependent field is not automatically removed when the value of the master field is changed.
In other words:
There is currently no way to safely use the Cascading model in Jira with conditionals applied, and this is frustrating since the issue is treated as a "suggestion" rather than an essential item to be prioritized.
The only way to safely use a cascading field today is by using the Select List Cascading field in the standard Jira form. However, it will be a static form, and you cannot use conditionals.
@eed34f8f8739 , there is no "Data Center equivalent bug" as the problem does not exist there.
@Atlassian - I don´t understand why this is a "Suggestion", this is clearly a bug. It creates invalid data and there is no way to prevent this, as there is no API to address the screens.
Please add support for Asset fields in Jira Expressions and we can maybe use Scriptrunner behaviours to clear fields or create validator for incorrect combinations !
I hope that this improvement will be added ASAP, it would be a great help. 
It seems incredible that a product included in premium JSM has errors of this type. We need a solution as soon as possible.
Thank you
Hello!
It is our intention to fix this. We are currently investigating a solution and looking into when we can schedule the work.
I'll provide further updates as this is scheduled in our roadmap.
All the best,
Justin King
Product Manager, Jira Service Management
Hello,
I took a look at this functionality and went through the cases which were reported in relation to this issue.
After reviewing the cases I recognize there is an expectation of field validation on top of the filtering which the Insight Filter Issue Scope offers.
Looking at the field functionality pattern across Jira, field input validation on based another field is unavailable.
Consistent with that experience we intended the Filter Issue Scope to be a filtering of input values based on the scope of the issue.
Once input occurs the boundary is reached and validation is outside of that scope.
I have considered the example of Select List(cascading) within our pattern. The field is behaving as one field for validation rather than two fields and is consistent with our issue field patterns.
I am transitioning this ticket to a suggestion so we may account for further open interest.
Thank you,
Radu
If Insight fields are added to Customer Portal of JSM, clients might manipulate those values and fill incorrect combination. And that is a high severity bug; provided workaround can barely be treated as workaround.
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.