• 1
    • 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.

      Atlassian status as of September 2019

      The Search Results macro allows you to display the results of a keyword search on a page. We are making some great changes to Search over the next few releases, and have observed that this macro is rarely used.

      We ended support for the Search Results macro in Confluence 7.0, and hid it from the macro browser. Any existing instances of this macro will still work, but you won't be able to insert this macro into the editor using the macro browser.

      End of support means Atlassian will not fix bugs related to this macro in Confluence 7.0 or later versions.

      To check whether a macro is used in your site, go to General Configuration > Macro Usage.

      Feel free to comment on this issue if this change will have a significant impact on your Confluence site.

      Find out more about our other planned changes in Confluence 7.0

            [CONFSERVER-57598] Plans to end support for the Search Results macro

            I agree with other commenters. I have several clients who rely on this macro HEAVILY. It does not seem that there is any similar functionality offered without implementing third-party add-ons or custom coding. This largely defeats the purpose of choosing Confluence over a FOSS solution where we know up-front there will be higher development costs. This is very disappointing - seems that the path should largely be third-party add-on > later incorporated into core, just as is the case historically with Drupal and Windows, just to name two prominent examples.

            Thomas Kermode added a comment - I agree with other commenters. I have several clients who rely on this macro HEAVILY. It does not seem that there is any similar functionality offered without implementing third-party add-ons or custom coding. This largely defeats the purpose of choosing Confluence over a FOSS solution where we know up-front there will be higher development costs. This is very disappointing - seems that the path should largely be third-party add-on > later incorporated into core, just as is the case historically with Drupal and Windows, just to name two prominent examples.

            David Pezet added a comment - - edited

            Our company heavily uses this macro. This macro combined with live page template macros and reporting macros is quite powerful and allows for dynamic searches to be included on pages to display related information very easily (simple example below). This can also be configured to dynamically search stored e-mails (snippet below), which there is not a current native alternative for (known to me).  This keeps from having to configure individual macros for every page with standard information types. Please reconsider continuing support. Obviously we'd prefer to keep this capability. Will there be a substitute macro that has the same or similar capabilities?  

            Snippet:

            <p>
            <ac:structured-macro ac:macro-id="3e8ca7cb-8aff-4891-be15-bfea7debfcbb" ac:name="search" ac:schema-version="1">
            <ac:parameter ac:name="maxLimit">1000</ac:parameter>
            <ac:parameter ac:name="query">"%page:title%"</ac:parameter>
            <ac:parameter ac:name="type">mail</ac:parameter>
            </ac:structured-macro>
            </p>

             

            David Pezet added a comment - - edited Our company heavily uses this macro. This macro combined with live page template macros and reporting macros is quite powerful and allows for dynamic searches to be included on pages to display related information very easily (simple example below). This can also be configured to dynamically search stored e-mails (snippet below), which there is not a current native alternative for (known to me).  This keeps from having to configure individual macros for every page with standard information types. Please reconsider continuing support. Obviously we'd prefer to keep this capability. Will there be a substitute macro that has the same or similar capabilities?   Snippet: <p> <ac:structured-macro ac:macro-id="3e8ca7cb-8aff-4891-be15-bfea7debfcbb" ac:name="search" ac:schema-version="1"> <ac:parameter ac:name="maxLimit">1000</ac:parameter> <ac:parameter ac:name="query">"%page:title%"</ac:parameter> <ac:parameter ac:name="type">mail</ac:parameter> </ac:structured-macro> </p>  

            Hi,

            @Emily Chan, we use this macro on 396 pages. It's a shame that you decided to remove it.

            Suggestion: next time you ask for a removal, please create a story named "Plans to CONTINUE support for the Search Results macro". If you say END, nobody will vote for it .

            Regards,

            Laurent

            Laurent Corbiere added a comment - Hi, @Emily Chan, we use this macro on 396 pages. It's a shame that you decided to remove it. Suggestion: next time you ask for a removal, please create a story named "Plans to CONTINUE support for the Search Results macro". If you say END, nobody will vote for it . Regards, Laurent

            Hi rbanwell439804261,

            Thank you for your feedback. We have decided that we will not be reversing our decision, so we will be ending support for this macro in Confluence 7.0.

            Best regards,

            Emily Chan

            Emily Chan (Inactive) added a comment - Hi rbanwell439804261 , Thank you for your feedback. We have decided that we will not be reversing our decision, so we will be ending support for this macro in Confluence 7.0. Best regards, Emily Chan

            Hi Emilie and Rachel,

            So, from what I understand this macro is still to be deprecated?

            For anyone like me, using Confluence Server, I assume that you have no way of knowing our usage of the Search Results macro. I use it on at least 100 pages according to my Macro Usage page...

            I understand that you have improved the overall search (we have just upgraded to Confluence Server 6.15) but Search Results allows those viewing our pages to see the results that we want them to, without having to choose the right options in the general Search...

            On top of the usage above, we use this for tracking changes such as our Client comments from our internal spaces.

            I look forward to hearing from you with more details of the situation.

            Kind regards,

            Rosalind BANWELL 

             

            Rosalind BANWELL added a comment - Hi Emilie and Rachel, So, from what I understand this macro is still to be deprecated? For anyone like me, using Confluence Server, I assume that you have no way of knowing our usage of the Search Results macro. I use it on at least 100 pages according to my Macro Usage page... I understand that you have improved the overall search (we have just upgraded to Confluence Server 6.15) but Search Results allows those viewing our pages to see the results that we want them to, without having to choose the right options in the general Search... On top of the usage above, we use this for tracking changes such as our Client comments from our internal spaces. I look forward to hearing from you with more details of the situation. Kind regards, Rosalind BANWELL   

            Rosalind BANWELL added a comment - - edited

            Hello,

            I wanted to let you know that the Search Results macro is very important to me (Confluence Server 6.13)!

            Example usage: As it's not possible to put tasks in comments, we use Search Results to provide a list of questions in comments addressed to our Product Owners (Search user.name NOT CLOSED-DOC)

            Rosalind BANWELL added a comment - - edited Hello, I wanted to let you know that the Search Results macro is very important to me (Confluence Server 6.13)! Example usage: As it's not possible to put tasks in comments, we use Search Results to provide a list of questions in comments addressed to our Product Owners (Search user.name NOT CLOSED-DOC)

              Unassigned Unassigned
              rrobins Rachel Robins
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: