@kkercz I mentioned this before in another post: The example in the documentation on entity properties is really misleading.
It shows how to store this content in the issue property tasks (plural!)
{“content”:“Test if works on Jira Cloud”, “completed” : 1}
The fact that it says tasks and the screenshot suggest that you can store multiple tasks in this property. I think readers of the documentation (like myself) then think that you could just store an array of tasks in the property (which you can) but then realize later that you can’t index an array at the property root.
The examples in the documentation do not match with the screenshot unless I am missing something or you use some fancy encoding to cramp multiple tasks into the same content and completed attribute.
Would be good if this documentation gets an overhaul and is very explicit about the fact that if you use anything other than an object as the property root, indexing won’t work.