Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-6395

Customer Request Type retaining Old Value in Issue Navigator

    XMLWordPrintable

Details

    Description

      Summary

      When moving a Service Desk Request to another issue type, the Request Type will change to "No Match" if none is selected when moving. But, it appears that if we search for the same moved issue in the Issue Navigator, the Customer Request Type is still retaining the Old Value rather than removed or "No Match"

      Steps to Replicate

      1. Create an SD Project.
      2. Create an Issue/Ticket
      3. Move the ticket to change the Issue Type
      4. Set the Customer Request Type to "No Match" and confirm the moving.
      5. Search for the issue in the Issue Navigator

      Expected Result

      The Request Type will be removed and shown as "No Match"

      Actual Result

      The old request type value is retained.

      Notes

      • Re-indexing does not helo
      • Different versions show different behavior:
        1. Jira Service Desk 3.12: in the issue list "No match" is shown
        2. Jira Service Desk 3.15: in the issue list the old customer request type is shown
        3. Jira Service Desk 4.1: in the issue list the old customer request type is shown

      Workaround

      • None to be found yet

      Attachments

        1. screenshot-1.png
          screenshot-1.png
          145 kB
        2. screenshot-2.png
          screenshot-2.png
          42 kB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jrahmadiputra Julian (Inactive)
              Votes:
              10 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync