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

Request Type shows incorrect value in New Issue View after performing Move action

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • Issue View
    • None

      Summary

      When performing the "Move" action from one issue type to another, the "Request Type" value stays the same, in reality when such a change is done, it should show "None".

      Steps to Reproduce

      1. Create a Service Desk ticket with a request type value
      2. In the new issue view, Move to another issue type with a different request type value

      Expected Results

      The request type value is empty.

      Actual Results

      The request type value has the same value as the previous issue type which is incorrect. If you change to "Old Issue View", it will show "No Match" for the request type, which is the expected outcome.

      Effect

      From the customer point of view, it is still visible and accessible despite having the wrong request type value. So the customer communication is still valid.

      Workaround:

      Switch to old issue view to key in the value in the "Request Type" field.

        1. sample_1.PNG
          sample_1.PNG
          24 kB
        2. sample_2.PNG
          sample_2.PNG
          27 kB
        3. sample_3.PNG
          sample_3.PNG
          24 kB

              rcrossman@atlassian.com Rachel Crossman
              nsilvaratnam Niro (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: