📣 Smart Values in CQL results (related entities) and For each task branches

[#1]

Hi there! Avinoam from Confluence Automation here 👋

We're excited to announce we'll be releasing some brand new smart values for you to use in Automation for Confluence very shortly! (more to come...) This will allow you to take further advantage of automation capabilities and tailor them to your use cases.

As a sneak peek, we want to notify you all that we will be adding more smart values to the outputs of the For each CQL result (related entities) branch and For each task branch. Both of these branches will now return relevant information such as {{page}}, {{blogpost}}, etc.

To avoid any confusion, these components will now clear preexisting content and space smart values prior to branching. If you need to use these smart values, you can use the Create variable action in order to preserve them.

We also just updated our support documentation to reflect this for your convenience!

Stay tuned for further updates! 😀

[Aron Gombas _Midori_]

@Avinoam CQL could be a killer feature in Confluence, like JQL is in Jira. The reality is that while the basic idea is great, there are surprising bugs:

1. Bugs in the specification. For example, you can't test if a content's parent is null?! There are other trivial fields  and operators and functions that should exist, but they don't.
2. Bugs in the implementation. For example, CONFCLOUD-74388 or CONFCLOUD-75314. These make searches randomly fail.

Given that these exist for multiple years, let me ask, is CQL a strategic feature for Atlassian?