I'm so sorry, can you start over with your explanation? And maybe include a screenshot that shows task 6? I'm just wondering what the status, and maybe other specifics of task 6 is (you've said it's a parent, you've said all children are complete, but you haven't specified if the parent is complete)...

You haven't really described how your Group Admins have added people in the past, so the only thing I can think of asking is if you have recently transitioned to Admin Console. In the meantime, as a workaround, are your admins able to copy an existing user and add people that way?

Your explanation of the errors you're experiencing are rather vague. I can point you to this link to help you along, but can't be more specific: https://experienceleague.adobe.com/en/docs/workfront/using/manage-work/requests/create-and-manage-request-queues/create-manage-request-queues   When you ar...

I think just the same way as always -- you add all three IDs on the same line, separated by tab spaces.

The syntax for that kind of thing would be to add the following to your current exists filter.   line 4: EXISTS:a:DE:projects:YourCustomField=_____line 5: EXISTS:a:DE:projects:YourCustomField_Mod=<your modifier>   The reason is below.   https://experienceleague.adobe.com/en/docs/workfront/using/repo...

if you're able to share your code, we can help troubleshoot. That said, I have submitted a bug because while it works in the calculation editor, my array calculation errors out on the actual form.   I heard a rumor at Summit that right now that the functionality is cosmetic and was unlocked in order...

If you look at the API explorer, the collection of tasks under your parent task will be referred to as "children" so it might be as simple as changing your "nested(tasks)" line to "nested(children)". I don't know if I should point out that this only acts on the next level down, so if you have grandc...

Starting a new thread to address clarifications made by the OP   EXISTS:a:$$OBJCODE=TASKEXISTS:a:actualStartDate_Mod=notnullEXISTS:a:name=buildEXISTS:a:name_Mod=cicontainsEXISTS:a:projectID=FIELD:projectIDEXISTS:b:$$OBJCODE=TASKEXISTS:b:actualCompletionDate_Mod=isnullEXISTS:b:name=asset auditEXISTS:...

Sven, sounds to me like: if in Project ABC, we have 5 tasks, 2 of which are the Asset Audit and Build tasks, the OP would like to see all 5 tasks whenever Asset Audit has not completed and Build has begun. So, 2 back-to-back exists statements either assuming there is only ever one Asset Audit and on...

yep that's a weird question for sure, so I wish they would clarify. I mean, it might be a NOTEXISTS filter with an AND statement on the names, assuming that you're able to distill both tasks down to "not CPL" but I would hate to struggle through it and waste my time.