I bet there are bunch of creative ways around this. Off the top of my head: Assign the placeholder task to a job role specifically for placeholder tasks. Use the filters in Workload Balancer to exclude those tasks. You could probably use a Team with similar effect.

Make sure you have filters in place. I've heard two different approaches: Product insists that you need Resource Pools in place to make Resource Planner work.Support told me that Resource Pools aren't required, that filters on something else should suffice. In this case, you should be able to filter...

@JenniferLegate We do. Requests: Ask for services.Issues: Flag something for correction, troubleshooting, or a bug.

@JenniferLegate That's a creative workaround for some, as long as you don't use issues. We use  both issues and requests, so this isn't viable for us.

@MoniqueEvans Leslie said you were interested in hearing more about the T-shirt sizing and scope creep. I suspect you know how I built it, but if anyone needs to see, it's on pages 13-14 in my attachment on [Event follow-up] November 2024 Skill Exchange: Wo... - Adobe Experience League Community - 7...

I had a blast! Thanks to everyone for entertaining my wild idea. At one point I glossed over how I proactively added calculations to my custom form in case I needed them. As a look behind the curtain, I created three calculations (shown in the screenshot below): LanguageRegionCountry (see screenshot...

That is not currently a function.

One way I workaround this is via the Share settings. As a result, I created a custom view that shows the Shared With value for the custom form. Naming conventions also help. I still support the idea, though, because there are flaws with my workaround.

A possible alternative is to use reporting to display these issues to each of your audiences. In other words, it doesn't matter where the issue goes because the report keeps a list based on your filters. One report is for the requestor, the other is for the people doing the work on the issue. You ca...

Here's an older thread where I share a couple templates I created from my own governance documentation. My knowledge base comes in a couple different forms:   Governance documentation (a.k.a. The Nerdy Details) I have many documents beyond the two linked in the above thread; basically one for each o...