-
Suggestion
-
Resolution: Won't Do
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
I see from the related issue that you did add CQL, but I was talking about using it Inside of a Macro to return CONTENT, not a just a list of pages from the search bar. I want to return content from pages by using CQL parameters. This would be useful.
You could match on labels, creation time, space, attachments, whether it has children, etc.
You could match on some of the attributes here:
https://developer.atlassian.com/static/javadoc/confluence/latest/reference/com/atlassian/confluence/pages/Page.html
I ran into the need when I wanted to include all of the pages of the children of a parent essentially the cross between the page include and the children include macros. However there were so many pages it would be very tedious to do so with page includes.
I started writing a macro for it, but I don't think we should need to make our own macros to do something so simple. The Macro I was writing nearly works, but it doesn't include the macros that are on the pages of the children, so all panels and other stuff are lost essentially.
Even that however, was a workaround for what I really needed.
What I really needed was to include the content of all children of a certain parents who matched a certain creation date. So I could have 1 dynamic page, whose content changed day to day based on which pages matched the creation date parameters. A shift log that would always have content from a time-span of 24-0 hours ago.
Now if CQL worked with the page include macro, then that would solve my issue.
- is cloned from
-
- Closed
- relates to
-
- Gathering Interest
[CONFSERVER-36546] CQL to return content WITHIN a Macro
| Workflow | Original: JAC Suggestion Workflow 4 [ 3579445 ] | New: JAC Suggestion Workflow 3 [ 4337589 ] |
| Workflow | Original: JAC Suggestion Workflow 2 [ 3185503 ] | New: JAC Suggestion Workflow 4 [ 3579445 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JAC Suggestion Workflow [ 3035625 ] | New: JAC Suggestion Workflow 2 [ 3185503 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2531852 ] | New: JAC Suggestion Workflow [ 3035625 ] |
| Resolution | New: Won't Do [ 10000 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Resolved [ 5 ] |
| Workflow | Original: Confluence Workflow - Public Facing v3 [ 2281411 ] | New: Confluence Workflow - Public Facing v4 [ 2531852 ] |
| Status | Original: Needs Verification [ 10004 ] | New: Gathering Interest [ 11772 ] |
| Workflow | Original: Confluence Workflow - Public Facing v3 - TEMP [ 2169729 ] | New: Confluence Workflow - Public Facing v3 [ 2281411 ] |
| Workflow | Original: Confluence Workflow - Public Facing v3 [ 1939796 ] | New: Confluence Workflow - Public Facing v3 - TEMP [ 2169729 ] |
| Workflow | Original: Confluence Workflow - Public Facing v2 [ 1756351 ] | New: Confluence Workflow - Public Facing v3 [ 1939796 ] |
Thank you for raising this suggestion.
We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.
For more context, check out our Community blog on our updated workflow for Suggestions
Cheers,
Confluence Product Management