Summary

      The JIRA Issue/Filter macro won't display the information contained on the Development field of software projects, and also the macro breaks after trying to reorder the issues using this field.

      Environment

      • Confluence cloud
      • Jira software

      Steps to Reproduce

      1. On a Confluence page insert a JIRA Issue/Filter macro.
      2. Configure a JQL which will return issues with the Development field.
      3. On the macro's view option, add the Development field.
      4. Save the macro and publish the page.
      5. Reorder the issues using the Development field.

      Expected Results

      • The information contained on the Development field/column should be shown along with the other fields.
      • After reordering the issues on the Development field/column, we should see all the information in the new order.

      Actual Results

      • The content of the Development field/column is not shown.
      • After reordering the issues using the Development field we receive an "Internal Server Error":

      Notes

      This might be related to the fact that the Development field is an array.

      Workaround

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

            [CONFCLOUD-65128] Development field is not shown on Jira issue macros

            Users don't really care whether the field is sortable, especially if it's not sortable in Jira itself. The bug here is:

            Development field is not shown on Jira issue macros

            Expected Results

            • The information contained on the Development field/column should be shown along with the other fields.

            Actual Results

            • The content of the Development field/column is not shown.

             

            For this not to be a bug, the Development field should not be shown at all in Confluence. But it can be shown, and doesn't display the same details as can be seen in Jira.

            Andy Nguyen - Atlassian team added a comment - Users don't really care whether the field is sortable, especially if it's not sortable in Jira itself. The bug here is: Development field is not shown on Jira issue macros Expected Results The information contained on the Development field/column should be shown along with the other fields. Actual Results The content of the Development field/column is not shown.   For this not to be a bug, the Development field should not be shown at all in Confluence. But it can be shown, and doesn't display the same details as can be seen in Jira.

            This field is unsortable

            zhikun xu (Inactive) added a comment - This field is unsortable

            This field is unsortable by design.
             

            zhikun xu (Inactive) added a comment - This field is unsortable by design.  

            Reta Pan added a comment -

            Hi Confluence Team,

            I meet the same issue, but currently it shows empty instead of error message of the original description.

            Please refer to the attached screenshot on PCS-140472.

            Thanks.

            Reta Pan added a comment - Hi Confluence Team, I meet the same issue, but currently it shows empty instead of error message of the original description. Please refer to the attached screenshot on PCS-140472 . Thanks.

            Hi all,

            As we are still facing this issue, so we decided to reopen this bug!

            We need to be able to export information from Bitbucket to Confluence.

            Henrique R (Inactive) added a comment - Hi all, As we are still facing this issue, so we decided to reopen this bug! We need to be able to export information from Bitbucket to Confluence.

            Hi everyone,
            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!

            Li Hsu (Inactive) added a comment - Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team!

              2797cdbebccd zhikun xu (Inactive)
              gtworkowski Guilherme T (Inactive)
              Affected customers:
              6 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated: