Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-81504

Custom Fields are missing in Jira Issue Macro

XMLWordPrintable

      Issue Summary

      Since upgrading to Confluence 7.3.1 to 7.19.1 customer is reporting that values of custom fields are not returning and not being displayed

      Bug Behaviour

      The behaviour of the bug is in such a way that if a user’s Jira Issue Macro has a custom fields to be returned from Jira, these fields are not retuned.

      Steps to Reproduce

      1. Install Confluence 7.3.1
      2. Install Jira 8.20.12
      3. Create a few issues on Jira with one custom field name Custom First and populate it
      4. Create an applink between Confluence to Jira
      5. Create a page named JIM731 in Confluence with a Jira Issue Macro with these property
        1. Filter: project = <Key of the project where the issue have been created>
        2. Field: Add Custom First to the field to display
      6. Upgrade Confluence to 7.19.1

      Expected Results

      Requested custom fields are returned from Jira to Confluence and displayed. 

      Actual Results

      Requested custom fields are empty in Confluence.

      Additional notes

      Storage format of the Macro which fails after upgrade to Confluence to 7.19.1:

      <p><ac:structured-macro ac:name="jira" ac:schema-version="1" ac:macro-id="aaa503f3-6574-4862-87d3-f6479f8fe76d"><ac:parameter ac:name="server">InstEnv Jira</ac:parameter><ac:parameter ac:name="columns">key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,custom first</ac:parameter><ac:parameter ac:name="maximumIssues">20</ac:parameter><ac:parameter ac:name="jqlQuery">project = MP </ac:parameter><ac:parameter ac:name="serverId">1131c139-68c6-3e50-86c7-8832ad59e376</ac:parameter></ac:structured-macro></p>

      Storage format of the macro created after upgrading:

      <p><ac:structured-macro ac:name="jira" ac:schema-version="1" ac:macro-id="dd735e93-3d1f-4cfd-aa24-0ffd5d0f1c23"><ac:parameter ac:name="server">InstEnv Jira</ac:parameter><ac:parameter ac:name="columnIds">issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution,customfield_10105</ac:parameter><ac:parameter ac:name="columns">key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,Custom First</ac:parameter><ac:parameter ac:name="maximumIssues">20</ac:parameter><ac:parameter ac:name="jqlQuery">project =MP </ac:parameter><ac:parameter ac:name="serverId">1131c139-68c6-3e50-86c7-8832ad59e376</ac:parameter></ac:structured-macro></p>

      The newly created macro has this additional section in it:

      <ac:parameter ac:name="columnIds">issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution,customfield_10105</ac:parameter>

      Workaround

      Delete and recreate the affected macro.

        1. screenshot-1.png
          screenshot-1.png
          147 kB

              3061d200deff Arpan Agrawal
              63948a2d3746 Marco Salvi
              Votes:
              35 Vote for this issue
              Watchers:
              42 Start watching this issue

                Created:
                Updated:
                Resolved: