Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-71741

Custom field types from Tempo are not populating in Jira issue macro

XMLWordPrintable

      Issue Summary

      Generally, it is possible to add custom fields in the columns to show in the Jira issue macro on Confluence, however, if the issue type/custom field is from the Tempo Plugin, this is not possible.

      Steps to Reproduce

      On Jira:

      1. Install the Tempo plugin from the Market Place
      2. On a Jira Project, create an issue and choose the issue type
      3. Go to the Project Settings > Screens and click on the default screen scheme for the issue type used in the issue created
      4. Add the Account custom field from Tempo in Configure Screen
      5. Go to the Tempo add-on (click on apps > ) > Account in the left sidebar
      6. Click on +Create Account and add the required information (Name, Key, Lead) and hit Create
      7. Click on the Account name just created and click on +Add Project Link
      8. Select the Project where you have created the jira issue

      On Confluence:

      1. Go to a Confluence Page
      2. Add the Jira issue macro
      3. Copy the link from the Jira issue and paste on the macro
      4. Click on Display Options and switch to Table
      5. On Columns to display, add the custom field Account (you can also add another custom field not related to tempo to compare)

      Expected Results

      The column would display the custom field from Tempo (e.g: Account)

      Actual Results

      The column from the custom field from tempo is not shown on the Jira issue macro, but other custom fields from Jira are.

      Workaround

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

              802848781776 Nick Yang
              jhonda@atlassian.com Jessica
              Votes:
              9 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: