Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-74593

Inconsistent patterns noticed while working with Component/s system field in Jira

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Medium
    • None
    • 9.2.0, 9.4.0, 8.20.22
    • None

    Description

      Issue Summary

      When using the Component/s and Affects Version/s System fields with increased length and number of values, the rendering of the values is very inconsistent in terms of display as well as how both fields appear in the same screen.

      All values are not displayed in the Component/s field and many times the hidden values (number) is not displayed, sometimes displayed on multiple lines, not allows editing sometimes and the problem is very inconsistent in nature.

      Reproducible in multiple browsers (Chrome & Safari Tested), different operating systems (Mac & Windows Tested), problem is reproducible in safe mode so this is not plugin specific.

      • Jira 9.2.0 (reproducible on multiple versions).
      • Chrome version used: 107.0.5304.110

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      1. Use a software project with Component/s and Affects Version/s fields enabled in the create/view issue screen.
      2. Add multiple values for both Component/s and Affects Version/s fields in the system fields. Use some large sized values for curiosity (number of words/letters).
      3. Create a Jira issue with multiple values populated for both these fields.
      4. Open the issue in a new browser in resized/windowed mode, or use active resizing the screen to visualize the problem better.
      5. While actively resizing the window option from right side, observe how the behaviour of the fields changes.

      Expected Results

      • Fields should always render additional data/records when possible OR show …(number).
      • Fields should always render additional data/records only once.
      • Fields should always render additional fields at the end of the field not multiple lines.
      • Commas should always be rendered on first line (Line breaks should not start with a comma).
      • Since both Component/s and Affects Version/s are system fields, they should have similar representation and consistent in nature.

      Actual Results

      • Fields is not showing the actual data/records - Ex Missing the …(10) at the end indicating no further values. In such scenario not able to edit values unless refreshed multiple times.
      • Fields shows additional data/records - but …(10) is rendered multiple(10) times.
      • Fields shows additional data/records - but …(10) is rendered in between to data/records.
      • Fields shows comma-separation on the next line, if fields is broken into multiple lines.
      • 'Affects Version/s' field spans across both the columns when large value is present upto certain limit while 'Component/s' field is scattered across multiple lines with similar length.
      • The appearance and rendering of the mentioned fields is not consistent and is very random in nature when multiple values are present.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              vyadavayyanamath@atlassian.com Vivek Yadavayyanamath
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: