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

JIRA issue macro in table view in Confluence does not link the page to JIRA

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

      The mentioned confluence page feature does not work in table view form. The mentioned in question is the feature as per the screenshot below :

      When JIRA issue macro is added to a Confluence page this will show the mentioned page in the JIRA ticket. However in table view this functionality does not work.

      Steps to reproduce :

      1. Login to Confluence
      2. Create a new page
      3. Add a jira macro by typing {JIRA then pick the first in the Macro suggestions
      4. A pop up window as per the screenshot below should come up then start searching for the JIRA issue
      5. Search for a JIRA issue, in this case I searched for TEST-3 and the results returned
      6. After that, click on the Display options and change it to Table as per the screenshot below :
      7. Click on Insert to complete the insertion to the page and you will see something like the screenshot below :
      8. Go to the JIRA issue in JIRA and you will not see the mentioned page :

      Expected result : the mentioned page should show
      Current result : the mentioned page is not shown

      This issue also occurs when I try it out in EAC with JAC.

        1. jiraIssueLink.jpg
          jiraIssueLink.jpg
          125 kB
        2. jiraIssuePopup.jpg
          jiraIssuePopup.jpg
          141 kB
        3. jiraIssueTable.jpg
          jiraIssueTable.jpg
          135 kB
        4. mentionFeature.jpg
          mentionFeature.jpg
          117 kB
        5. tableView.jpg
          tableView.jpg
          163 kB

            [CONFCLOUD-39845] JIRA issue macro in table view in Confluence does not link the page to JIRA

            Nick Mileson added a comment - - edited

            Here's my work around.

            • Add a collapsible element in Confluence page
            • Get a list of Jira links and paste in collapsible element
              • I use Excel to build an incremented list of numbers
              • Then VS Code to select all with carriage returns with Ctrl+d
              • Then paste the Jira link prefix
            • Paste all links as Plain Text into collapsible element
            • All issues in table are hack-ably linked!
            • PROFIT! 

            Nick Mileson added a comment - - edited Here's my work around. Add a collapsible element in Confluence page Get a list of Jira links and paste in collapsible element I use Excel to build an incremented list of numbers Then VS Code to select all with carriage returns with Ctrl+d Then paste the Jira link prefix Paste all links as Plain Text into collapsible element All issues in table are hack-ably linked! PROFIT! 

            This is quite important Issue.
            The point is that using "Jira Issue table" view, you are able to see relevant information inside the Jira Issue (Description, labels...) that are not shown in the "Jira Single Issue" view.
            For this reason we are using table view, and it is quite anoying that the Jira ticket "mentioned in" is not working properly.

            Arturo Colina Marin added a comment - This is quite important Issue. The point is that using "Jira Issue table" view, you are able to see relevant information inside the Jira Issue (Description, labels...) that are not shown in the "Jira Single Issue" view. For this reason we are using table view, and it is quite anoying that the Jira ticket "mentioned in" is not working properly.

            Not only is it not resolved, it is not being considered: 

            Marwan Osman added a comment - Not only is it not resolved, it is not being considered: 

            I cannot fathom that this is a bug in the first place and that it is still not resolved...

            Bas Muller added a comment - I cannot fathom that this is a bug in the first place and that it is still not resolved...

            Considering that after 4+ years this is not going to be fixed, does anyone know any workarounds?

            Juan Sueiro added a comment - Considering that after 4+ years this is not going to be fixed, does anyone know any workarounds?

            When do you plan to fix that bug?

             

            Gerald Maresch added a comment - When do you plan to fix that bug?  

            Chris Gado added a comment -

            This is still an issue? We are in progress of adopting the Atlassian toolkit and managing the collaboration needed for complex design. We need the ability to track these issues as a table inside Confluence to plan agendas and capture meetings notes. Then having he seamless integration to being able to view the notes while reviewing the issues in Jira. 

            This is clearly a bug. We cannot individually link dozens of issues after creating the macro.

            Chris Gado added a comment - This is still an issue? We are in progress of adopting the Atlassian toolkit and managing the collaboration needed for complex design. We need the ability to track these issues as a table inside Confluence to plan agendas and capture meetings notes. Then having he seamless integration to being able to view the notes while reviewing the issues in Jira.  This is clearly a bug. We cannot individually link dozens of issues after creating the macro.

            This is an extremely irritating bug in the Jira Macro for Confluence.  We are having to workaround by creating two macros, one in single line for and other in table format.  Really not good that this hasn't been fixed after nearly 5 years.  

            Also, interesting to note that the equivalent issue for Confluence Server has been changed from a Bug to a Suggestion!!  It's clearly a bug.

            Pete Singleton added a comment - This is an extremely irritating bug in the Jira Macro for Confluence.  We are having to workaround by creating two macros, one in single line for and other in table format.  Really not good that this hasn't been fixed after nearly 5 years.   Also, interesting to note that the equivalent issue for Confluence Server has been changed from a Bug to a Suggestion!!  It's clearly a bug.

            Completely Agree with Angga. This makes using the Atlassian Ecosystem taste bitter.

            Marwan Osman added a comment - Completely Agree with Angga. This makes using the Atlassian Ecosystem taste bitter.

            Why is this bug categorized as minor? do we have any workaround for this?
            it has been reported for more than 4 years already...

            Angga Wiratama added a comment - Why is this bug categorized as minor? do we have any workaround for this? it has been reported for more than 4 years already...

              Unassigned Unassigned
              dooi Der Lun
              Affected customers:
              58 This affects my team
              Watchers:
              50 Start watching this issue

                Created:
                Updated: