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

Request type configuration interface causes confusion when editing and causes fields to lose their place on the Issue view

XMLWordPrintable

    • 2
    • 55
    • 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.

    • Hide
      Update 15 May 2023

      Please be aware that we have not scheduled any development work on this in the next two quarters. We will provide another update around October 2023.

      However, your input remains incredibly valuable to us. We encourage you to keep voting and providing feedback. Every vote and piece of feedback informs our future priorities and helps us understand your needs better.

      Thank you for your understanding and your continued support.

      Regards,
      Simon
      JSM - Principal Product Manager

      Show
      Update 15 May 2023 Please be aware that we have not scheduled any development work on this in the next two quarters. We will provide another update around October 2023. However, your input remains incredibly valuable to us. We encourage you to keep voting and providing feedback. Every vote and piece of feedback informs our future priorities and helps us understand your needs better. Thank you for your understanding and your continued support. Regards, Simon JSM - Principal Product Manager

      Issue Summary

      When ordering fields on the Request form tab, the fields on the issue view are re-ordered. In this scenario, the fields are present on both the request form and the issue view, but the order is not maintained for each and instead, just uses the order of the Request form tab and places the field in the right side bar of the Issue view tab with the text Request form.

      Steps to Reproduce

      1. Go to the Issue view tab of a request type
      2. Place a field in between two other fields on the form
      3. Save changes
      4. Open or refresh an already existing request (that is using this same request type) and observe the fields are where they were placed on the Issue view tab
      5. Click on the Request form tab
      6. Move that same exact field from the right side bar (where it has the text Issue view) onto the form in a different location
      7. Save changes
      8. Confirm the order on the request type form in the portal
      9. Refresh the already open request and see that the field order setup on the Issue view tab was not maintained and that it is now using the order that was setup on the Request form tab

      Expected Results

      The field should both still be shown on the form in the Issue view tab (as the current method of removing it from the form and placing it on the side bar with the text Request form is confusing), but it should also maintain its previous position/order on that same tab.

      Actual Results

      The field is removed from the form on the Issue view tab and placed onto the side bar with the text Request form and also loses its position in the Issue view tab (using the Request form tab as well).

      Workaround

      If a Project Settings > Form is used, the field displayed in the Issue View can be used in the request portal form without impacting its location in the issue view.  More details on forms are available here 

              96677a1d9b4c Sam Knight
              mmarney@atlassian.com Matthew M. (Inactive)
              Votes:
              24 Vote for this issue
              Watchers:
              37 Start watching this issue

                Created:
                Updated:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 50m
                  50m