Hi,   You're correct, if you have removed a users ability to view tasks in their access level, they will also lose access to task information displayed in reports.   An approach you could take would be to set the report to run with the access rights of an admin (Edit Report >> Report settings >> Run...

Hi Bill,   It depends on a number of factors such as which licensing model your are on and which plan. Customers on old licensing aren't restricted, but if you're on the new model the number of proof decisions is limited for contributors.    This question is probably best directed to your CSM as the...

Hi,   The ability to customise the branding of your Workfront instance is no longer supported.   Best Regards, Rich

Hi,   The following text mode should do it:   textmode=true group.0.displayname=Hour Type group.0.valueexpression=IF({hourType}="Task Time"||{hourType}="Issue Time","Billable","Non Billable") group.0.valueformat=string   Best Regards, Rich.

Hi,   In your queue settings, under Queue Details >> New Issue Fields, do you have "Planned Completion Date" checked?     Best Regards, Rich.  

Hi,   Yes, spot on. Requests will need to be converted into tasks, or projects with tasks to get the same behaviour.   In Workfront, Requests are generally seen as just that, an "ask" for work to be done. They don't represent work that has been committed to, or planned into your Workflow. The act of...

Hi Himanshu,   It depends what object types these fields are on. . . .   If you have the same field on different forms, but on the same object (i.e., two forms on the same project. The forms have the same field on each), then populating one field will automatically populate the second field with the...

Hi Justin,   Assuming that "project category" is a custom field that is attached to projects, the following text mode view in a proof approval report should do the trick:   displayname=Project Categorylinkedname=documentVersionnamekey=view.relatedcolumnnamekeyargkey.0=documentVersionnamekeyargkey.1=...

Hey,   Using the below in your calculation should do the trick:   {owner}.{homeTeam}.{name}   You don't need the "CONCAT" operator in your expression since you're only pulling one value into the field.   Best regards, Rich.

Hey,   Give the following a go and let me know if this works   EXISTS:1:$$EXISTSMOD=NOTEXISTSEXISTS:1:$$OBJCODE=DOCFLDEXISTS:1:documentID=FIELD:IDOR:1:EXISTS:a:$$EXISTSMOD=EXISTSOR:1:EXISTS:a:$$OBJCODE=DOCFLDOR:1:EXISTS:a:documentID=FIELD:IDOR:1:EXISTS:a:folder:name=finalOR:1:EXISTS:a:folder:name_Mo...