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

Asset field display the object from linked issue when moved back to parent issue(doesn't refresh/reload)

XMLWordPrintable

      Issue Summary

      While performing a URL redirect on the browser between the Linked issues, the asset field is not updated until the page is reloaded.

      Steps to Reproduce

      1. Create an issue where the Asset field is part of the side panel.
      2. Then create a task/linked issue where the Asset field is also part of the side panel.
      3. Navigate back to the parent request using the <- button on the browser.
      4. We notice the Asset is listing the object from the Linked issue.
      5. Replication video:- https://share.getcloudapp.com/geuEvNgm 

      Expected Results

      • The asset field should get refreshed and show the actual data

      Actual Results

      Asset field shows the object selected as part of linked issue

      Workaround

      Reload the page and the issue gets fixed.

            [JSDCLOUD-12289] Asset field display the object from linked issue when moved back to parent issue(doesn't refresh/reload)

            Clyde Smets (Inactive) added a comment -

            We've identified the issue and have applied a fix. It is now resolved and working as expected.

            Clyde Smets (Inactive) added a comment - We've identified the issue and have applied a fix. It is now resolved and working as expected.

            Matthew Pavlovich added a comment -

            Agree with Alan Rowe and Rob Bennemeer.

            This needs to be a higher priority as it impacts operational effectiveness, decision making and can cause data integrity issues ie BSM.

            When an Agent is investigating a ticket, especially if they are under pressure on a high impact incident, what they see on the screen needs to be contextually correct without second guessing.

            As soon as they click on any other issue link (ie via linking, subtask etc) from that starting issue, it will visually show all asset custom fields that are reused between the different issues as the same, but will show other asset custom fields that arent shared between issues correctly.

            This bug makes the excellent value of what asset fields can do questionable to use in any business critical process.

            This is a Duplicate of JSDCLOUD-13018

            Matthew Pavlovich added a comment - Agree with Alan Rowe and Rob Bennemeer. This needs to be a higher priority as it impacts operational effectiveness, decision making and can cause data integrity issues ie BSM. When an Agent is investigating a ticket, especially if they are under pressure on a high impact incident, what they see on the screen needs to be contextually correct without second guessing. As soon as they click on any other issue link (ie via linking, subtask etc) from that starting issue, it will visually show all asset custom fields that are reused between the different issues as the same, but will show other asset custom fields that arent shared between issues correctly. This bug makes the excellent value of what asset fields can do questionable to use in any business critical process. This is a Duplicate of JSDCLOUD-13018

            Alan Rowe added a comment - - edited

            I believe JSDCLOUD-13018 is a duplicate / variant of this same issue.

             

            [e] I'd also humbly suggest that the bug is worse than Minor, as it is making my users pull their hair out trying to replace or remove values that don't represent the actual value of the ticket they are viewing.

            [e2] JSDCLOUD-12246 results in similar symptoms.

            Alan Rowe added a comment - - edited I believe JSDCLOUD-13018 is a duplicate / variant of this same issue.   [e] I'd also humbly suggest that the bug is worse than Minor, as it is making my users pull their hair out trying to replace or remove values that don't represent the actual value of the ticket they are viewing. [e2] JSDCLOUD-12246 results in similar symptoms.

            rob.bennemeer added a comment -

            It's a cross browser issue. Tested with Chrome and Firefox.

            rob.bennemeer added a comment - It's a cross browser issue. Tested with Chrome and Firefox.

              90325da67d46 Mohamed Hassan
              d3e338d93ca5 SivaKalyan G
              Affected customers:
              33 This affects my team
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: