@CassieSt - if you utilize request queues for users to request projects then this is how they are setup. Technically, all requests are issues tied to a "project".   Create a Request Queue | Adobe Workfront

This sounds like an issue with Admin console. I would suggest opening a support ticket.    

Description - When assigning a task to a team, that team can include Light Users. Light users don't have access to make assignments to others or themselves, even though they are on the team (fine, understood). However, through the UI, the user is presented with options to do so. If the user clicks ...

Try this expression instead   ROUND(DIV(WORKMINUTESDIFF({actualCompletionDate},{actualStartDate}),480),2)

I've had a few engaging conversations lately around access levels and permissions in Workfront. Here are a couple of narratives I've heard: Custom access levels are imperative for system governanceIf I'm paying for users to have X license, they should be able to do everything with that license for t...

Is the report being looked at by or run with the rights of another user who doesn't have access to the issues in question? 

I would start by verifying you are pulling the fields from the correct object type in the column picker.   Sometimes, when fields are on forms that can be used on multiple objects, the fields will appear in the report builder under those different object types. Example - For this task report, if I w...

You would also need to add a statement for your other status.    valueexpression=IF({canStart}=true && {status}!='CPL' && {status}!='CNC" && {numberOfChildren}=0,CONCAT("•",{name}))  

They should show in the updates section of the document.   Some things you can check: Make sure the comments weren't made on a "private stage" through the proofing workflow. Verify the system access level allows comments to be viewed and that the "only view updates in which they have been included i...