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...

We use them periodically for different things. The one sticking point we've run into is that for some reason, those specific emails get routed to Junk Mail a LOT by Outlook, even when all the ordinary notifications coming from the same email arrive just fine. I finally put together this single slide...

So the solution to fix what they broke is to pay them for hundreds of unnecessary new licenses. That's...convenient. Looks like I need to start evaluating other vendors to handle our request queue functionality soon.

I've done some recordings for Support from our instance, and demonstrated a proof-of-concept for how I will use external lookup fields to circumvent the bug/security issue if necessary. Hopefully they will be able to address this quickly. 

Confirming the same behavior in our instance. I'm going to open a bug report with Support on it. There's no way they intentionally put a single typeahead field behind a paywall to require us to convert hundreds of users to paid licenses on purpose, I'm sure. Hopefully it will be fixed quickly, or my...

Good afternoon, The Workfront feature you need to support that goal is called a 'Schedule'. Once created, the Schedule can be applied to either an individual user and/or a project itself. Applying the schedule to a user will ensure that the resourcing areas of Workfront reflect their availability co...

Almost a year later, and my team just brought this exact same issue up on my office hours call. Any progress on fixing this behavior? I'm currently working with a test user where I set the schedule to CST, their timezone to CST, and updated both my computer and browser timezone to CST and it's still...