I have successfully done the whole "cascading selection" with Asset object custom fields using the Filter issues scope. This is great, when the primary issue field has been populated so that the second issue field can filter based on that. However I would like for the second issue field to still show every object it can if the first issue field hasn't been populated yet. Basically, I don't want the second issue field to be dependent on the first issue field, but only helped by it, if it's populated.
Specifically, the behavior I want is:
1. Asset object issue field called "Area" exists on issue but is empty
2. Asset object issue field called "Building" exists on issue and shows all available objects, as if it's Filter issue scope was empty.
3. I populate the "Area" field on the issue
4. The "Building" field on the issue now shows filtered objects that have the same Area attribute value (object) as the one selected in step 3
Note that the Building objects will have an "Area" attribute linked to an "Area" object, same as the issue in the primary field (customfield_10315)
I wasn't expecting is not EMPTY and is EMPTY to work in AQL since I couldn't find any documentation on it. The AQL validator says the code is ok, however when I check the issue, the "Building" field is not showing any objects at all now
Also, I know that the objectType = objectTypeAndChildren("Structures") part in the Filter issue scope section is repetitive, I was just trying to give it something to validate against in case that was required. I've also removed it and left just ${customfield_10315} is EMPTY on the right side of the OR and it still isn't working
I've also tried using an IF statement but couldn't get that to work either.
I'm open to any ideas\suggestions
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.