Ehm...I'd hoped for better news, but I now agree that this one is essentially hopeless, Brian. If I'm following, you're trying to find Projects that meet two conditions:
a specific Task ("submit materials") is present, and
the Project's originating Issue did not have the expected Category ID on it (i.e. was raised as the wrong type)
To create a Project report that matches the first condition, I suggest adding a textmode filter like this:
tasks:name=submit materials
tasks:name_Mod=cicontains
To further restrict those Projects to only those that whose originating Issue does not match the expected Category (e.g. "Name Of Expected Category"), I WOULD have suggested adding additional textmode to the filter similar to this:
convertedOpTaskID_Mod=notnull convertedOpTask:category=Name Of Expected Category convertedOpTask:category:name_Mod=eq
However, convertedOpTaskID is only accessible via "https://support.workfront.com/hc/en-us/articles/115002672154-Deprecating-Customer-Use-of-API-Internal">api-unsupported (meaning the standard Workfront reports can't get at it), and even through api-unsupported, convertedOpTask:category:name (and even convertedOpTask:categoryID) do not support Searching (meaning even it would be very tricky, even using our "http://store.atappstore.com/product/magic-reports/">Magic Reports solution). Although small consolation, I at least encourage you to stop banging your head against the wall on this one. Regards, Doug
Doug Den Hoed - AtAppStore Got Skills? Lend a hand!
https://community.workfront.com/participate/unanswered-threads
