This are the queue topics in my admin queue personally. Absolutely possible, and then it feeds into a Board I use to manage requests with my team. 

@lgaertner is correct that there is no easy way to accomplish your task. Within a Report, you could easily create a calculated column that referenced the collection of project team members to get that data, but calculated fields on a form do not support that functionality. If you have a stakeholder ...

If you are using the Kanban board feature as part of the Agile team setup, the only Status options that can be supported are locked System Status level ones. This is because the Tasks/Issues that flow into those boards can come from theoretically anywhere within the instance, so the status options m...

If there is a maximum, my teams have never complained about it yet. And I've got folks that will create one program per project just because it makes sense to them. So there might be a limit but it's WAY out there if so. 

Just as every record in Workfront has a unique system-generated ID, so to does every record in Salesforce. I'd find some field on the Document object in Workfront to store the unique document ID from Salesforce. I'd try extRefID myself so it's something hidden from users. Once you have that, you hav...

Has your problematic field EVER been a multi-select, even if it's single-select now? That makes me wonder if there isn't historical data from an old config of the field where multiple options could be selected. 

Seconding this answer. That lack of key functionality is what makes the Proof tool useless in my instance, unfortunately. 

We started seeing that last week, but I didn't have time to make a video of the whole thing and write the required essay to have Support review it. We do not use any of the features related to rate cards/roles or any financial functionality at all.

I would suggest the same as Skye, I don't allow communal accounts in our instance for exactly that reason. No ability to audit who really made what changes.  This is also likely a violation of Adobe's ToS as it could be seen as an attempt to avoid purchasing the correct number of licenses you actual...

I can tell you that your base API URL matches what I have working in my Postman sandbox to our Jira Cloud instance. I can also tell you that getting the authentication working was an exercise in patience. I'd string together that base URL and put it right into your browser. If you get results there,...