Jira Automation: #for and #if block helpers fail with functions and arrays

Question

Smart value block helpers (#if, #for) in Jira Automation fail or behave inconsistently when using functions inside, especially with dynamic property access, array iteration, and function calls in block conditions or within loops.

Example-

Given config = [{"version": "1.2.3", "env": "PROD"}, {"version": "1.2.4", "env": "TEST"}]
When attempt to iterate and filter using -

{{#for(jsonStringToObject(config))}}
   {{#if(equals(version, "1.2.4"))}}
      {{env}}
   {{/if(equals(version, "1.2.4"))}}
{{/for(jsonStringToObject(config))}}

Then 
-this produces no output (empty),
- no error is shown,
- documentation is unclear if this feature has issues.

Expected result:
- Block helpers should support function calls and dynamic conditions,
- If not supported, documentation should clearly state the limitations and advise a roadmap.

Any suggestions?

Joshy Chirayath · Answer

Thank you . Yes, it helped me resolve one issue where I could use the lookup table action.

I also had the "more data than just the key / value pairs" case that needed a comparison instead of match operation. I've commented re that under your article https://community.atlassian.com/forums/Automation-articles/Automation-concepts-Dynamic-searches-within-a-list/ba-p/2834235

Thanks again, much apprciated.

Bill Sheboy · Answer

Hi @Joshy Chirayath

Just following up to check if this answered your question.  If so, please consider marking this one as "answered".  That will help others with a similar need find solutions faster.  If not, please let the community know what help you need with the rule changes.

Thanks!

Bill Sheboy · Answer

Awesome; I am glad to learn that helped!

Regarding using the variable for the list filter, that will not work directly: there is a long-standing limitation where only data from the iterator scope, and lower, can be accessed inside a long-format iterator.

Here is one of the open defects / suggestions for that limitation.

With Jira Cloud and your specific scenario, there are two possible workarounds:

* Using the data converted to JSON, and the Create Dynamic Lookup Table action, load your version and env as key / value pairs and get the value needed from the table.* action: create dynamic lookup table * name: varConfigTable
* dynamic source: {{jsonStringToObject(varMyJson).config}}
* key: version
* value: env

* Then use thisVersion to get() the value: {{varConfigTable.get(thisVersion)}}

* For cases with more data than just the key / value pairs, a dynamic search method with regular expressions can help.  Here is an article I wrote describing the method: https://community.atlassian.com/forums/Automation-articles/Automation-concepts-Dynamic-searches-within-a-list/ba-p/2834235