great job! It's good syntax (which means you're now officially an API explorer expert), but not a possible filter.
Troubleshooting tips: you can tell it's a good filter, because a similar filter would work in a project report. i.e. the following syntax works in a PROJECT report:
convertedOpTaskOriginator:homeTeamID=$$USER.homeTeamID
convertedOpTaskOriginator:homeTeamID_Mod=in
Moving it into your TASK report, now! This won't work, (probably) because it's too many levels? Read this section "Overview of object relationships in Workfront" and tell me what you think. https://experienceleague.adobe.com/docs/workfront/using/reporting/reports/text-mode/create-complex-t...
[Further troubleshooting for masochists: if your code works in a VIEW but not a FILTER then it's too many levels.]
Obviously this makes the solution quite clear -- you need to back out your last two lines, and replace it with an exists filter. So take a look at this sample code:
EXISTS:a:$$OBJCODE=PROJ
EXISTS:a:ID=FIELD:projectID
EXISTS:a:convertedOpTaskOriginator:homeTeamID=$$USER.homeTeamID
line 1: there exists a project...
line 2: where the project's ID is the same as your task's projectID field...
line 3: and in this project, the original requester's home team is the same as your user's home team.
