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

JIRA issue macro does not display certain columns data(work ratio, progress field, time to resolution and time to first response)

XMLWordPrintable

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      The problem

      Our documentation states the following "You can include any columns recognised by your JIRA site, including custom columns", however when including a JIRA Macro issue in a Confluence page and including the fields work ratio, or progress the value of those fields is not displayed.

      This affects JIRA Service Desk "Time to resolution" and "Time to first response".

      Steps to reproduce:

      1. In JIRA issue search screen identify the issues that have some value in the fields wrok ratio. or progress:
      2. Insert a JIRA Macro issue into a Confluence page using the same JQL and edit the columns to display:
      3. Save the page and the following will be displayed:

        1. Confluence_page.png
          Confluence_page.png
          38 kB
        2. JIRA_Issue_macro_config.png
          JIRA_Issue_macro_config.png
          92 kB
        3. JIRA_search.png
          JIRA_search.png
          60 kB
        4. Screen_Shot_2014-10-08_at_5_24_20_PM.jpg
          Screen_Shot_2014-10-08_at_5_24_20_PM.jpg
          416 kB

            [CONFSERVER-35196] JIRA issue macro does not display certain columns data(work ratio, progress field, time to resolution and time to first response)

            John Just added a comment -

            Still not working in 8.5.17.

            John Just added a comment - Still not working in 8.5.17.

            Christophe MOUCHATI added a comment -

            Idem, I have the same problem and I didn't see the answer.

            Thank you for your help

            Christophe MOUCHATI added a comment - Idem, I have the same problem and I didn't see the answer. Thank you for your help

            Matthias Schouten added a comment -

            I had the same issue with my Jira. As a workaround you I used the dashboard gadget "Filter Result", added that as a external gadget to Confluence and used that on my page instead of the default macro

            https://confluence.atlassian.com/doc/registering-external-gadgets-204050482.html

             

             

            Matthias Schouten added a comment - I had the same issue with my Jira. As a workaround you I used the dashboard gadget "Filter Result", added that as a external gadget to Confluence and used that on my page instead of the default macro https://confluence.atlassian.com/doc/registering-external-gadgets-204050482.html    

            Antonio Smith added a comment -

            work ratio

            I was so excited to bring in this field for our stakeholders to quickly get a progress without having to share ticket level updates to find it doesn't pull in any data. 

            Antonio Smith added a comment - work ratio I was so excited to bring in this field for our stakeholders to quickly get a progress without having to share ticket level updates to find it doesn't pull in any data. 

            Karl Kreutzwiesner added a comment -

            Any news to that ? 

            Karl Kreutzwiesner added a comment - Any news to that ? 

            John Smith added a comment -

            Still the same with Confluence 7.18.1

            John Smith added a comment - Still the same with Confluence 7.18.1

            John Smith added a comment - - edited

            Same here

            8 years, really?
            Priority High?

            Confluence 7.14.1
            Jira 8.22.2

             

            John Smith added a comment - - edited Same here 8 years, really? Priority High? Confluence 7.14.1 Jira 8.22.2  

            Constantin Tran added a comment -

            Same here, but with Start date and End Date -. -

            Constantin Tran added a comment - Same here, but with Start date and End Date -. -

            LPS Config Team added a comment -

            Same issue here with a custom field

            LPS Config Team added a comment - Same issue here with a custom field

            NiYunfan added a comment -

            Following

            Hope that could be fixed...

            NiYunfan added a comment - Following Hope that could be fixed...

              05a8667aef42 Saquia Naz
              tcomasseto Tiago Comasseto
              Affected customers:
              187 This affects my team
              Watchers:
              171 Start watching this issue

                Created:
                Updated: