I see: it's about statuses. I've heard others recommend keeping statuses relatively simple because, as you've discovered, managing them is sometimes not easy. Defining clear governance around statuses can help reduce how often someone asks for a new status. For example, in our organization we use: N...

I might not entirely follow what you're suggesting, but I've thought a lot about our own group structure, so I'll share what we've done. We use the Companies field and Groups. Here's how it works: Companies: The vast majority of users fall under our actual company name. I create a new company when w...

I think it depends on what you need for historical data. When I overhauled our groups, I didn't know what I didn't know and just went for it. Fortunately no one came screaming in protest. That said, if you have a need to hold onto historical data, calculated custom fields can be super helpful. For e...

We tried to go this direction, so I've spent a lot of time thinking and planning for it. Right now we have about half of Marketing and two non-Marketing groups actively using Workfront, which means we have use cases for both siloing work and cross-COE collaboration.   User setup Groups are important...

I'm interested to hear what you mean by "technical debt." Having inherited an aged and loosely managed instance in the past, I learned a few things along the way. I'll start with the soft tactics: It's important to talk to your users to get an idea of what they use and don't use.Communicate to make ...

I agree with @Erika_Antkowiak to keep it simple where possible. I include topics and, after most of those topics, prompt for: DescriptionURLPrimary contactDocuments There are some topics that I associate a custom form with, especially around user management. Topics I include largely mirror areas of ...

Automated proof workflows are ideal for standarized process. Basic workflows are ideal for simple workflows or when you need more control over the variables. My organization has so many variables with proofing, especially around the users who should be on the proof, that we lean toward basic.

I, too, could probably use some clarification around what you're trying to accomplish. That said, let's see if this information helps: Routing rules are designed to help you either move an issue to another project and/or assign the issue.In the absence of any routing rules (because it's not required...

@CR17506599 This is an existing setting for fields, so you wouldn't need to set it via validation logic. It exists below the Instructions field. See the screenshot attached.

For our instance, system administration takes the lead on most everything because we don't have a strong culture of group administration. In that case, I use group admins as more of an advisory council. For our instance, a group admin earns more freedom when they've: Completed trainingConsistently c...