Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-10496

When using Assets object cascading fields, the dependent field value doesn’t get removed automatically when the master field value is changed

    • 432
    • 11
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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

      1. Create 2 Insight object custom fields: Country and City
      2. Master field: Country and Dependent field: City
      3. For Country value Italy, the City values are VeniceRome
      4. For Country value Germany, the City values are BerlinBonn
      5. In Country field select Italy and in dependent field City set Rome.
      6. Change the Country to Germany but the City field still shows Rome unless manually changed.
      7. 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.

          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

            (23/08/2022) 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.

            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.

            Nathon Fowlie added a comment - (23/08/2022) 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. 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.

            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?

            Tobias Bosshard added a comment - 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?

            +1

            +1

            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.

            Muhammet Ayal added a comment - 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.

            Josh added a comment -

            +1

            This fix is desperately needed.

            Josh added a comment - +1 This fix is desperately needed.

            Letícia Deus added a comment - - edited

            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.

            Letícia Deus added a comment - - edited 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.

            Thomas Heidenreich (//S) added a comment - - edited @ 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.

            TomaszJ added a comment -

            Hi, is there a Data Center equivalent bug created for this issue? 

            TomaszJ added a comment - Hi, is there a Data Center equivalent bug created for this issue? 

            +1

            Oleksii Melnyk added a comment - +1

              90325da67d46 Mohamed Hassan
              cf3a9e2a2246 Diptajeet Datta
              Votes:
              240 Vote for this issue
              Watchers:
              109 Start watching this issue

                Created:
                Updated: