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

Unable to select auto-complete result in User Picker custom field

      Summary

      Unable to select a value from User Picker (single user) custom field in JIRA 6.3.15

      Environment

      JIRA 6.3.15
      JIRA Agile 6.6.60, 6.6.70

      Steps to Reproduce

      1. Create a User Picker (single user) custom field
      2. Associate it to the Default Screen
      3. Navigate to an Agile Board, click the Create button to trigger the pop-up window
      4. Enter some value to trigger the auto-complete
      5. Try to click any user from the result

      Expected Results

      User is able to select the auto-complete result

      Actual Results

      User is unable to select the auto-complete result

      Notes

      If the action is performed from an Agile Board view, this javascript error will be thrown:

      An error occurred
      Please try refreshing the page, or contact your administrator / Atlassian Support if the problem continues.
      Details

      Environment
      Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36

      Stack trace

      Workaround

      1. Create issue normally without selecting the User Picker value. Edit the issue afterward, to update the field
      2. Fill in the username without selecting the auto-complete result
      3. Access the create issue screen in http://your.jira.com/secure/CreateIssue!default.jspa . The User Picker custom field is working correctly there

            [JRASERVER-42145] Unable to select auto-complete result in User Picker custom field

            Hi alexis1,

            This was fixed in 6.4.1 so I suspect you are seeing a very similar but different problem in your instance. Can you please raise a support ticket with us at https://support.atlassian.com so that we can investigate further what is going and help you on this matter.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi alexis1 , This was fixed in 6.4.1 so I suspect you are seeing a very similar but different problem in your instance. Can you please raise a support ticket with us at https://support.atlassian.com so that we can investigate further what is going and help you on this matter. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            I get this same error in 6.4.11 when I try to link against fisheye. So the potential fix mentioned above is not working since the quick edit plugin is already version 2.4.17...

            Alexis Wilke added a comment - I get this same error in 6.4.11 when I try to link against fisheye. So the potential fix mentioned above is not working since the quick edit plugin is already version 2.4.17...

            Unfortunately, that is the case atlassian_admin. The JIRA bugfix team only delivers fixes on the last maintenance release of JIRA and currently that is the JIRA 6.4.x maintenance release series.

            We hope that you can upgrade soon to get the fix for this issue. Should you need support during your upgrade please do not hesitate to contact us at https://support.atlassian.com and we will be glad to help you with any issues you run into during your upgrade if necessary.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Unfortunately, that is the case atlassian_admin . The JIRA bugfix team only delivers fixes on the last maintenance release of JIRA and currently that is the JIRA 6.4.x maintenance release series. We hope that you can upgrade soon to get the fix for this issue. Should you need support during your upgrade please do not hesitate to contact us at https://support.atlassian.com and we will be glad to help you with any issues you run into during your upgrade if necessary. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            Hi

            So no updates will be available for Jira 6.3.15???
            We can't move to the latest 6.4.x yet !!!!

            Regards,
            Areg

            ARM Ltd. (old account) added a comment - Hi So no updates will be available for Jira 6.3.15??? We can't move to the latest 6.4.x yet !!!! Regards, Areg

            Carl Corliss added a comment - - edited

            This actually looks like a problem we (at my company) are experiencing as well. I managed to track our issue down to the decorateFields method of the JIRA.Forms.CreateIssueHelper object. The problem we are experiencing lies in what that method is attaching onchange events to:

              decorateFields: function(){
                var A=this;
                this.form.$element.find('*[id^="customfield_"]').off("change.customField").on("change.customField",function(){
                  A.form.model.markFieldAsDirty(this.name)
                })
            

            Generally speaking, the above works - except for custom fields that are wrapped in div containers. Custom fields wrapped in div containers also share an id tag starting with customfield_ (e.g., <div id="customfield_10000-wiki-edit">). This causes the onchange event to be attached to not only the input field (in our case, a textarea field) but, also the div containing the input field.

            What would probably fix the issue is if, instead of searching for id starting with customfield_, the search was for name starting with customfield_, e.g.:

              decorateFields: function(){
                var A=this;
                this.form.$element.find('*[name^="customfield_"]').off("change.customField").on("change.customField",function(){
                  A.form.model.markFieldAsDirty(this.name)
                })
            

            Carl Corliss added a comment - - edited This actually looks like a problem we (at my company) are experiencing as well. I managed to track our issue down to the decorateFields method of the JIRA.Forms.CreateIssueHelper object. The problem we are experiencing lies in what that method is attaching onchange events to: decorateFields: function(){ var A= this ; this .form.$element.find( '*[id^= "customfield_" ]' ).off( "change.customField" ).on( "change.customField" ,function(){ A.form.model.markFieldAsDirty( this .name) }) Generally speaking, the above works - except for custom fields that are wrapped in div containers. Custom fields wrapped in div containers also share an id tag starting with customfield_ (e.g., <div id="customfield_10000-wiki-edit">). This causes the onchange event to be attached to not only the input field (in our case, a textarea field) but, also the div containing the input field. What would probably fix the issue is if, instead of searching for id starting with customfield_, the search was for name starting with customfield_, e.g.: decorateFields: function(){ var A= this ; this .form.$element.find( '*[name^= "customfield_" ]' ).off( "change.customField" ).on( "change.customField" ,function(){ A.form.model.markFieldAsDirty( this .name) })

            Please upgrade this bug to critical one

            Everyone else open a support case so they fix this in a minor version of 6.3.15

            Jóhann B. Guðmundsson added a comment - Please upgrade this bug to critical one Everyone else open a support case so they fix this in a minor version of 6.3.15

            This happens on the create screen with multi user picker on 6.3.15 which prevents sub-tasks being created

            Jóhann B. Guðmundsson added a comment - This happens on the create screen with multi user picker on 6.3.15 which prevents sub-tasks being created

            Also when you are on Agile Board the "." keyboard shortcut does not work as Agile JS is completely replacing it ....

            AregVrtanesyan added a comment - Also when you are on Agile Board the "." keyboard shortcut does not work as Agile JS is completely replacing it ....

            AregVrtanesyan added a comment - - edited

            Hi
            This is actually not Jira problem.
            This is Agile problem as you need to be on Agile Board to reproduce it.
            Looks like that Agile is adding some JS which is clashing with the Jira JS.

            May be it is necessary to review error and see if it is applies to the Agile?

            An error occurred
            Hide…
            
            Please try refreshing the page, or contact your administrator / Atlassian Support if the problem continues.
            Details
            
                    Exception: TypeError: A is undefined
                    Resource: http://jira/s/bfde23f7522d534a68a003b2f32b00b2-T/en_UK12azbc/6346/4/07c0ce1d99603585af87d8045344428b/_/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.global/batch.js?locale=en-UK&isAdmin=true
                    Line: 992
                    Column: 38
            
            Environment
            Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0
            Stack trace
            
                JIRA.Forms.CreateIssueModel<.isCustomFieldId@http://jira/s/bfde23f7522d534a68a003b2f32b00b2-T/en_UK12azbc/6346/4/07c0ce1d99603585af87d8045344428b/_/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.global/batch.js?locale=en-UK&isAdmin=true:992:39
                JIRA.Forms.CreateIssueModel<.normalizeCustomFieldId@http://jira/s/bfde23f7522d534a68a003b2f32b00b2-T/en_UK12azbc/6346/4/07c0ce1d99603585af87d8045344428b/_/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.global/batch.js?locale=en-UK&isAdmin=true:994:41
                JIRA.Forms.CreateIssueModel<.markFieldAsDirty@http://jira/s/bfde23f7522d534a68a003b2f32b00b2-T/en_UK12azbc/6346/4/07c0ce1d99603585af87d8045344428b/_/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.global/batch.js?locale=en-UK&isAdmin=true:989:1
                JIRA.Forms.CreateIssueHelper<.decorateFields/<@http://jira/s/bfde23f7522d534a68a003b2f32b00b2-T/en_UK12azbc/6346/4/07c0ce1d99603585af87d8045344428b/_/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.global/batch.js?locale=en-UK&isAdmin=true:1071:111
                d.event.dispatch@http://jira/s/d3de83f8447cb14709bd960d40788633-CDN/en_UK12azbc/6346/4/3/_/download/superbatch/js/batch.js?locale=en-UK:74:451
                d.event.add/i@http://jira/s/d3de83f8447cb14709bd960d40788633-CDN/en_UK12azbc/6346/4/3/_/download/superbatch/js/batch.js?locale=en-UK:66:252
            
            

            Regards,
            Areg

            AregVrtanesyan added a comment - - edited Hi This is actually not Jira problem. This is Agile problem as you need to be on Agile Board to reproduce it. Looks like that Agile is adding some JS which is clashing with the Jira JS. May be it is necessary to review error and see if it is applies to the Agile? An error occurred Hide… Please try refreshing the page, or contact your administrator / Atlassian Support if the problem continues. Details Exception: TypeError: A is undefined Resource: http: //jira/s/bfde23f7522d534a68a003b2f32b00b2-T/en_UK12azbc/6346/4/07c0ce1d99603585af87d8045344428b/_/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.global/batch.js?locale=en-UK&isAdmin= true Line: 992 Column: 38 Environment Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0 Stack trace JIRA.Forms.CreateIssueModel<.isCustomFieldId@http: //jira/s/bfde23f7522d534a68a003b2f32b00b2-T/en_UK12azbc/6346/4/07c0ce1d99603585af87d8045344428b/_/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.global/batch.js?locale=en-UK&isAdmin= true :992:39 JIRA.Forms.CreateIssueModel<.normalizeCustomFieldId@http: //jira/s/bfde23f7522d534a68a003b2f32b00b2-T/en_UK12azbc/6346/4/07c0ce1d99603585af87d8045344428b/_/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.global/batch.js?locale=en-UK&isAdmin= true :994:41 JIRA.Forms.CreateIssueModel<.markFieldAsDirty@http: //jira/s/bfde23f7522d534a68a003b2f32b00b2-T/en_UK12azbc/6346/4/07c0ce1d99603585af87d8045344428b/_/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.global/batch.js?locale=en-UK&isAdmin= true :989:1 JIRA.Forms.CreateIssueHelper<.decorateFields/<@http: //jira/s/bfde23f7522d534a68a003b2f32b00b2-T/en_UK12azbc/6346/4/07c0ce1d99603585af87d8045344428b/_/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.global/batch.js?locale=en-UK&isAdmin= true :1071:111 d.event.dispatch@http: //jira/s/d3de83f8447cb14709bd960d40788633-CDN/en_UK12azbc/6346/4/3/_/download/superbatch/js/batch.js?locale=en-UK:74:451 d.event.add/i@http: //jira/s/d3de83f8447cb14709bd960d40788633-CDN/en_UK12azbc/6346/4/3/_/download/superbatch/js/batch.js?locale=en-UK:66:252 Regards, Areg

            @Remo: Thanks for the work-around, has solved the problem for me too.

            Robert Meerman added a comment - @Remo: Thanks for the work-around, has solved the problem for me too.

              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              dwatania@atlassian.com Daniel Watania (Inactive)
              Affected customers:
              19 This affects my team
              Watchers:
              27 Start watching this issue

                Created:
                Updated:
                Resolved: