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

Adding multiple single user picker fields to customer portal causes some fields to not be editable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest
    • 5.0.0, 4.20.8, 4.22.2
    • 4.22.0, 4.20.6
    • Customer Portal
    • None

      Issue Summary

      Users are unable to edit some user picker fields in the customer portal when multiple user picker fields are present.

      Steps to Reproduce

      1. Create 3 or more custom fields of type User Picker (single user)
      2. Add these fields to the customer portal (Project settings > Request Types)
      3. Load the customer portal

      Expected Results

      All user picker fields are editable

      Actual Results

      Not all user picker fields are editable. Some will only show the label and the drop down will be missing.

       

      The following error is also visible on the browser's console:
       

      batch.js?locale=en-BR:2186 Uncaught TypeError: Cannot read properties of undefined (reading 'split')
          at Object.created (batch.js?locale=en-BR:2186:20460)
          at l (batch.js?locale=en-BR:768:370)
          at c (batch.js?locale=en-BR:769:40)
          at c (batch.js?locale=en-BR:769:199)
          at c (batch.js?locale=en-BR:769:199)
          at c (batch.js?locale=en-BR:769:199)
          at c (batch.js?locale=en-BR:769:199)
          at c (batch.js?locale=en-BR:769:199)
          at c (batch.js?locale=en-BR:769:199)
          at c (batch.js?locale=en-BR:769:199)
      

      Workaround

      Replacing servicedesk-frontend-plugin jar file via plugin directory.

      • If JSM was installed as the first application, the directory would be: 
        • atlassian-jira/WEB-INF/application-installation/jira-servicedesk-application
      • If JSM was installed as the 2nd application, using obr, the directory would be:
        • <shared-home>/plugins/installed-plugins

      Steps

      Prepare Jira 8.20.5/4.20.5 installation:

      1. Go to atlassian-jira/WEB-INF/application-installation/jira-servicedesk-application or <shared-home>/plugins/installed-plugins (see the points above)
      2. Copy servicedesk-frontend-plugin-4.20.5-REL-0003.jar

      On Jira 8.20.6/4.20.6 installation > go to the same directory

      1. Stop Jira on all nodes
      2. Remove servicedesk-frontend-plugin-4.20.6-REL-0005.jar
      3. Add servicedesk-frontend-plugin-4.20.5-REL-0003.jar
      4. Start Jira and perform a full reindexing

       
      If it's atlassian-jira/WEB-INF/application-installation/jira-servicedesk-application directory, then apply this on all nodes. However, if it's <shared-home>/plugins/installed-plugins, then just apply it once in the shared-home directory.

      Remember to perform this in the staging instance first, before applying it in the production.

            [JSDSERVER-11136] Adding multiple single user picker fields to customer portal causes some fields to not be editable

            Surender added a comment -

            You can get the jar file from JSM v4.20.5. Thanks!

            Surender added a comment - You can get the jar file from JSM v4.20.5. Thanks!

            N Thatte added a comment - - edited

            We are observing same issue with three Single User Picker fields on a form. 

            I would also like to know, where can we download the 4.20.5 version jar file? 

            N Thatte added a comment - - edited We are observing same issue with three Single User Picker fields on a form.  I would also like to know, where can we download the 4.20.5 version jar file? 

            Experiencing this issue w/ 8.22 and 4.22. Can Aqqiela or yyao provide instructions for JSM 4.22 or confirm servicedesk-frontend-plugin-4.20.5-REL-0003.jar will work for 4.22? And where do we get that jar file from?

            Andrew Januszak added a comment - Experiencing this issue w/ 8.22 and 4.22. Can Aqqiela or yyao provide instructions for JSM 4.22 or confirm servicedesk-frontend-plugin-4.20.5-REL-0003.jar will work for 4.22? And where do we get that jar file from?

            We've found another workaround for our issue, again our pages with the issue have one single-user and one multi-user. The single was first and the multi would not populate. We tested reversing their order and both work now. I'm going to check with the project owner to see if that's good for a temporary solution.

            Michael Johnson added a comment - We've found another workaround for our issue, again our pages with the issue have one single-user and one multi-user. The single was first and the multi would not populate. We tested reversing their order and both work now. I'm going to check with the project owner to see if that's good for a temporary solution.

            We have request pages with only one single-user and one multi-picker and we're seeing the issue with the multi(it's second on the pg). A page refresh will populate it as well as linking directly to the request page or opening in a new tab from the main page.

            Michael Johnson added a comment - We have request pages with only one single-user and one multi-picker and we're seeing the issue with the multi(it's second on the pg). A page refresh will populate it as well as linking directly to the request page or opening in a new tab from the main page.

            We are also seeing this behavior when the 3rd (or greater) user picker field is a multi-user picker. Basically any user picker after the second single user picker seems to be affected.

            Amanda Lenczewski added a comment - We are also seeing this behavior when the 3rd (or greater) user picker field is a multi-user picker. Basically any user picker after the second single user picker seems to be affected.

            Also affected from this and looking forward to the 4.20.x release with a fix.

            Patrick Albrecht added a comment - Also affected from this and looking forward to the 4.20.x release with a fix.

            Hi all,

            We are experiencing the same issue. It seems that if the page is refreshed that the other drop down fields load correctly - this is the workaround our organisation is currently making use of.

            lmollentze@gew.co.za added a comment - Hi all, We are experiencing the same issue. It seems that if the page is refreshed that the other drop down fields load correctly - this is the workaround our organisation is currently making use of.

            Ryan Carl added a comment -

            +1

             

            Ryan Carl added a comment - +1  

            James added a comment -

            +1

            James added a comment - +1

              cf304d525cce yyao (Inactive)
              astegani Alex Stegani
              Affected customers:
              18 This affects my team
              Watchers:
              36 Start watching this issue

                Created:
                Updated:
                Resolved: