Uploaded image for project: 'SR for Jira - Development'
  1. SR for Jira - Development
  2. SRJIRA-2138

Elements Connect (formerly nFeed) fields not compatible with behaviours



    • Bug
    • Status: Done
    • Low
    • Resolution: Won't Fix
    • 4.3.4,, 4.3.15,
    • None
    • None
    • None
    • 25.3


      There are several issues that come up when an nFeed field is included as part of a behaviour.

      Assigning Behaviour to nFeed field throws error

      nFeed custom fields cause error Exception: Uncaught TypeError: Cannot read property 'fieldType' of undefined when behaviour assigned to them.

      Requiring an nFeed Field May Break Other Behaviours

      If someone marks an nFeed field as required in a behaviour, then another field in the behaviour marked as Read Only may still be editable.

      Read-only Creates brown box around label

      When configuring an nFeed field to appear on a particular screen (for example edit screen) and then mapping a behaviour to that field that sets the field to be read-only a brown box appears around the label of the field. This can be seen in the attached screenshot.

      You get something that looks like this in the DOM:

      <div class="field-group">
         <label for="customfield_10008" disabled="disabled" class="clientreadonly">Feed</label>
         <div style="width:100%;">
            <input type="hidden" name="nfeedFieldPreset" value="customfield_10008">
            <select name="customfield_10008" style="width:0;height:0;position:absolute;opacity:0;" multiple="multiple" tabindex="-1"></select>
            <div style="display:inline-block; width:100%;">
               <div name="component" class="nfeed-component" style="display: block;">
                  <div class="select2-container long-field aui-select2-container nfeed-select2" id="s2id_autogen3">
                     <a href="javascript:void(0)" class="select2-choice select2-default" tabindex="-1">   <span class="select2-chosen" id="select2-chosen-4">Type to search</span><abbr class="select2-search-choice-close" style="display: none;"></abbr>   <span class="select2-arrow" role="presentation"><b role="presentation"></b></span></a><label for="s2id_autogen4" class="select2-offscreen"></label><input class="select2-focusser select2-offscreen" type="text" aria-haspopup="true" role="button" aria-labelledby="select2-chosen-4" id="s2id_autogen4">
                     <div class="select2-drop select2-display-none aui-select2-drop aui-dropdown2 aui-style-default nfeed-select2 select2-with-searchbox aui-layer" resolved="" aria-hidden="true">
                        <div class="select2-search">       <label for="s2id_autogen4_search" class="select2-offscreen"></label>       <input type="text" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false" class="select2-input" role="combobox" aria-expanded="true" aria-autocomplete="list" aria-owns="select2-results-4" id="s2id_autogen4_search" placeholder="">   </div>
                        <ul class="select2-results" role="listbox" id="select2-results-4">   </ul>
                  <select class="long-field" tabindex="-1" title="" style="display: none;">
                     <option value="10000"></option>
            <div name="in_progress" class="button-spinner" style="margin-top: -5px; margin-left: 5px; display: none;"></div>
            <div class="description nfeed-error" style="display:none;">
               <span class="aui-icon aui-icon-small aui-iconfont-error" style="color: red;"></span>
               <span class="message-text"></span>
            <div class="description nfeed-message" style="display:none;">
               <span class="message-text"></span>
            <div class="description nfeed-warning" style="display:none;">
               <span class="aui-icon aui-icon-small aui-iconfont-error" style="color: darkorange;"></span>
               <span class="message-text"></span>

      We should look at why its applying the clientreadonly class to the label.

      JS error when creating issue from rapid board

      Also when mapping a behaviour to an nFeed field that exists on the create screen you get a JavaScript error when clicking create issue from the rapid board view. This prevents users from creating issues.


        Issue Links



              Unassigned Unassigned
              amarkham Adam Markham
              11 Vote for this issue
              32 Start watching this issue