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

Σ Remaining Estimate Does Not Show Any Values in JIRA Issues Macro

XMLWordPrintable

      Atlassian Update - 29 July 2019

      After some analysis we've found that this issue has been duplicated by the issue at CONFSERVER-34149 - JIRA Issue Macro not showing value for Σ Remaining Estimate. This is a current and verified bug in Confluence, please watch that issue for further updates.

      Σ Remaining Estimate does not return any value despite having values in Σ Original Estimate and Σ Time Spent columns.

      How to Reproduce

      1. Create a new issue or task in JIRA. (let's say ABC)
      2. Create a couple of sub-tasks under the ABC task.
        Log some time into the tasks respectively for best results.
      3. Connect Confluence and JIRA via Application Links configuration panel.
      4. Create a new page in Confluence.
      5. Insert JIRA Issues macro via "+" sign in the editor toolbar.
      6. Under Search tab, insert the related ABC tasks (which includes the sub-tasks) or use a JQL. For example:
        project = "ABC"
      1. Use the following display options. (Key, Summary, Issue Type, Due Date, Assignee, Priority, Status, Σ Original Estimate, Σ Time Spent, Σ Remaining Estimate, Original Estimate, Time Spent, Remaining Estimate)
      2. Click Insert to confirm and add the JIRA Issues macro to the page.
      3. Observe the value in the Σ Remaining Estimate column.

      Expected Behaviour

      All values are shown in the columns.

      Actual Behaviour

      Σ Remaining Estimate value is missing.

        1. display.png
          display.png
          384 kB
        2. conf-jira.png
          conf-jira.png
          216 kB

              Unassigned Unassigned
              kyong Kok Yan Yong (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: