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

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

XMLWordPrintable

    • 2
    • 6
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? 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. mentionFeature.jpg
          117 kB
          Der Lun
        2. jiraIssueLink.jpg
          125 kB
          Der Lun
        3. jiraIssuePopup.jpg
          141 kB
          Der Lun
        4. jiraIssueTable.jpg
          135 kB
          Der Lun
        5. tableView.jpg
          163 kB
          Der Lun

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

            Vigil Vijayan added a comment -

            Please advise an ETA for the raised issue.

            Vigil Vijayan added a comment - Please advise an ETA for the raised issue.

            Gaétan POULAIN added a comment -

            Hello,

            I have the same problem : JIRA issue macro in table view in Confluence does not link the page to JIRA.

            Could you inform when the bug will be resolved ?

            Thanks

            Gaétan POULAIN added a comment - Hello, I have the same problem : JIRA issue macro in table view in Confluence does not link the page to JIRA. Could you inform when the bug will be resolved ? Thanks

            Jeremy Mordkoff added a comment -

            I understand that this will have a performance impact, in fact I can't imagine how you would implement this idea so that it worked in real time in all cases.  After changing any Jira issue, you would have to then run every query in confluence to see if this change affected the output (which implies caching the output of every query) and update the mentions.  Add to that, what if the query had a clause like "assignee=currentUser()" ? And I suppose it must be possible for a query to select based on related issues, so changing Jira issue X could cause the mentions to change on Jira issue Y.

            However this feature is too important not to address. How do I explain to my users that some mentions are shown and others are not? Keep in mind that my confluence users are not the most technically gifted people in my company. Asking them to replace a Jira query that returns 50 items with 50 individual items is insane when the whole point of the query is that it updates in real time when Jira changes. 

            So.... my "spec" 

            Any queries that could generate different results for different users should be flagged, the mentions suppressed and  the user creating the macro should be warned that this is happening. 

             Given that you have that. there should also be an option to suppress the creation of mentions when creating a Jira macro in confluence. For instance I have personal confluence pages that generate lists of tickets for the members of my team. I don't want them reminded of that fact every time they open a Jira. 

            implementation ... 

            Adding or removing mentions in Jira is easy when the confluence page is changed, especially if the results are cached. 

            Removing a mention when the Jira is changes is also easy .. you could just re-execute the queries on any page listed as a mention today and remove the mention if the issue no longer is in the result. 

            Adding a mention when the Jira is changed is trickier. I would suggest that this could be implemented as a background task that is triggered by edits in Jira. It's frequency should be configurable, all the way up to immediate (unless an instance was already running) or it could self-regulate based on load. 

            To be honest, I was shocked when I found this ticket. I had assumed that the mentions just worked. And I can't believe this has been open for years. Please reconsider implementing this soon.

             

            Jeremy Mordkoff added a comment - I understand that this will have a performance impact, in fact I can't imagine how you would implement this idea so that it worked in real time in all cases.  After changing any Jira issue, you would have to then run every query in confluence to see if this change affected the output (which implies caching the output of every query) and update the mentions.  Add to that, what if the query had a clause like "assignee=currentUser()" ? And I suppose it must be possible for a query to select based on related issues, so changing Jira issue X could cause the mentions to change on Jira issue Y. However this feature is too important not to address. How do I explain to my users that some mentions are shown and others are not? Keep in mind that my confluence users are not the most technically gifted people in my company. Asking them to replace a Jira query that returns 50 items with 50 individual items is insane when the whole point of the query is that it updates in real time when Jira changes.  So.... my "spec"  Any queries that could generate different results for different users should be flagged, the mentions suppressed and  the user creating the macro should be warned that this is happening.   Given that you have that. there should also be an option to suppress the creation of mentions when creating a Jira macro in confluence. For instance I have personal confluence pages that generate lists of tickets for the members of my team. I don't want them reminded of that fact every time they open a Jira.  implementation ...  Adding or removing mentions in Jira is easy when the confluence page is changed, especially if the results are cached.  Removing a mention when the Jira is changes is also easy .. you could just re-execute the queries on any page listed as a mention today and remove the mention if the issue no longer is in the result.  Adding a mention when the Jira is changed is trickier. I would suggest that this could be implemented as a background task that is triggered by edits in Jira. It's frequency should be configurable, all the way up to immediate (unless an instance was already running) or it could self-regulate based on load.  To be honest, I was shocked when I found this ticket. I had assumed that the mentions just worked. And I can't believe this has been open for years. Please reconsider implementing this soon.  

            Roman Jedlička added a comment -

            Will you solve this problem?

            Roman Jedlička added a comment - Will you solve this problem?

            Marwan Osman added a comment -

            @Confluence Product Management, it has been over 12 months time now. This issue is still a problem for us.

            Marwan Osman added a comment - @Confluence Product Management, it has been over 12 months time now. This issue is still a problem for us.

            Adam Barnes (Inactive) added a comment -

            This issue has been moved from a Bug to a Suggestion as Confluence has never provided the functionality requested.

            Whilst the logic behind this request is sound, the performance impact to accomplish the desired result would have a profound impact on Jira and Confluence.

            This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.

            Cheers,

            Confluence Product Management

            Adam Barnes (Inactive) added a comment - This issue has been moved from a Bug to a Suggestion as Confluence has never provided the functionality requested. Whilst the logic behind this request is sound, the performance impact to accomplish the desired result would have a profound impact on Jira and Confluence. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status. Cheers, Confluence Product Management

            Adam Sterrie added a comment - - edited

            Hi abarnes@atlassian.com,

            This is really bad for Atlassian's reputation. You create a blueprint for requirements telling users how easy it will make their lives then you miss off one of the unique selling points about Confluence (i.e. it's tight integration with Jira) by removing the "mentioned in" link in the newly created tickets. Now user's have to create the link manually so that the link to the Confluence page appears in the Jira ticket table of links. Moreover, it takes users a while to figure out that he functionality is broken. You saved failure from the jaws of success. Now whenever a Jira admin wants to sell a new feature of Confluence that will make their users' lives easier, the users are going to wonder where the catch is and if they should bother learning how to use the new feature and then having to find out where all the bugs are.

            Aren't you embarrassed to say "there is no plan to look at this". In what universe is it "logical behaviour" to explicitly mention a Jira ticket in a Confluence page and not add a "Mentioned in" link to the ticket to the Confluence page? Is that the latest euphemism for "bug"?

             

            Adam S.

            Adam Sterrie added a comment - - edited Hi  abarnes@atlassian.com , This is really bad for Atlassian's reputation. You create a blueprint for requirements telling users how easy it will make their lives then you miss off one of the unique selling points about Confluence (i.e. it's tight integration with Jira) by removing the "mentioned in" link in the newly created tickets. Now user's have to create the link manually so that the link to the Confluence page appears in the Jira ticket table of links. Moreover, it takes users a while to figure out that he functionality is broken. You saved failure from the jaws of success. Now whenever a Jira admin wants to sell a new feature of Confluence that will make their users' lives easier, the users are going to wonder where the catch is and if they should bother learning how to use the new feature and then having to find out where all the bugs are. Aren't you embarrassed to say "there is no plan to look at this". In what universe is it "logical behaviour" to explicitly mention a Jira ticket in a Confluence page and not add a "Mentioned in" link to the ticket to the Confluence page? Is that the latest euphemism for "bug"?   Adam S.

            James Greene added a comment -

            Hi abarnes@atlassian.com,

            If there's no plan to address this, is there a way to add/edit the fields that are shown (other than key/summary/status) for the Single issue view?  If that exists (or did exist) even in a limited fashion, it would be very helpful.

             

            James G.

            James Greene added a comment - Hi  abarnes@atlassian.com , If there's no plan to address this, is there a way to add/edit the fields that are shown (other than key/summary/status) for the Single issue view?  If that exists (or did exist) even in a limited fashion, it would be very helpful.   James G.

            Adam Barnes (Inactive) added a comment -

            Hi fabrice.huart754192035, there is no immediate plan to look at this.

            It logically makes sense to expect this behaviour for a single issue in a table, but starts to become more convoluted with multiple entries.

            The real issue lies in the fact that the table in Confluence is computed at the time the page is rendered and therefore it is not possible for Jira to know whether or not a particular issue would be displayed on a page at any given point in time.

            I see this issue as more a feature request than a bug as the behaviour is by design.

             

            Adam - Confluence PM

            Adam Barnes (Inactive) added a comment - Hi fabrice.huart754192035 , there is no immediate plan to look at this. It logically makes sense to expect this behaviour for a single issue in a table, but starts to become more convoluted with multiple entries. The real issue lies in the fact that the table in Confluence is computed at the time the page is rendered and therefore it is not possible for Jira to know whether or not a particular issue would be displayed on a page at any given point in time. I see this issue as more a feature request than a bug as the behaviour is by design.   Adam - Confluence PM

            Fabrice Huart - NSI added a comment -

            Hi,

            This is a blocking issue for us.

            When will you have a look at it ?

            Best regards,

            Fabrice

            Fabrice Huart - NSI added a comment - Hi, This is a blocking issue for us. When will you have a look at it ? Best regards, Fabrice

              Unassigned Unassigned
              dooi Der Lun
              Votes:
              52 Vote for this issue
              Watchers:
              45 Start watching this issue

                Created:
                Updated: