When you use a kickstart, you are creating new records somewhere in Workfront. It's not just a disconnected Excel sheet hanging out with no context. That can be a set of tasks, issues, projects etc. It uploads to wherever you code it to upload to. If your form is a task-level form, then you could de...

To be fair, I only thought of that eventually because I remembered the late night /I/ spent swearing at it right after the feature went live! Glad you're on the right path now.

When you say 'it's doing nothing' - WHERE is it doing nothing? When you try and test in Preview via the form designer? Or when you actually go to a record with that form/field attached and test there? If you're trying to see it work in Preview, then that's the actual issue. The logic doesn't fire in...

In the example HERE, it shows the equals comparison as a double sign. Have you tried that one yet? I know I have some with '!=' working as expected.      

You're very close I think. Give this edit a try to start. You have to at least give if the 'false' criteria for sure.   IF({DE:Who is creating your communication?}="pods","Pods-based materials cannot be reviewed in this queue.","")   If that still doesn't work, check: 1. Case sensitivity - Is the dr...

The only other obscure option could be if the admin has dragged those options way down in their navigation menu so they're below everything else, and for some reason their browser isn't showing them the scroll down menu. But otherwise once you're a Sys Admin, the only way I know of to hide anything ...

The other thing I'd check is that the Program is Active. I've run into that a few times in our instance.

Put a ticket into Support. I ran into that too, and when you delete a status sometimes it doesn't fully release the Key you previously used somewhere in the database. They can fix it for you though. I can look up whatever my ticket number for it was if they aren't sure how to help initially.

Each record in WF has an associated reference number, but I wouldn't expect the reference number of the original issue to change. The resulting project would have it's own separate reference number though. Are you seeing the original issue's number changing? 

This is worth trying to fix, we've definitely had a couple cases where an internal employee tagged an external customer from the wrong customer in a discussion by accident. I've seriously considered branching access levels so only people who work with external customers can even see them in the list...