hi Kristen, I have it working in the sandbox. The project custom form contains field "expense account #" The calculated field I have at the issue level is: Project.{expense account #} and I also put another "expense account #" field in there. I set up a queue to handle creating the issue, and when I...

Kirsten, I'm not seeing why that wouldn't work, unless the project custom field is changed after the issue is created. If this is the case, the issue's custom form needs to be resaved to trigger the information to carry over again. -skye

I think it's important to remember that any custom field you create can be used on a form that attaches to a specific object . And you can create many different forms (you just created an issue and a project form using the same field, for example). with this in mind, if you're on a task custom form,...

hey Kathy, sorry, I mis-typed. I was more wondering if you assign Workfront "training tasks" to reviewers or not. -skye

I'm not a reporting expert but... I think the truer statement is probably that you can often inline edit reports and the trick is to make sure that the fields you are trying to edit are on the object that you're reporting about. For example if I wanted to EDIT a project's planned completion date, I'...

hey Kathy, what do you do about users who are Reviewer licenses? (or does this not occur?) Otherwise, we have similar. I have a dashboard for inactive users and an Outlook reminder to check it every quarter. I check all paid licenses to make sure they are still employees and if they are and haven't ...

thanks Greg! At the moment we're trying for a Fusion integration with AD to bring a few more fields from AD to map to custom fields in Workfront. The sticking point is that the permissions appear to go both ways (so from a fusion perspective it would be easy[??] for me to make a change to AD, which ...

Thanks Dustin. I think I'm just going to hang tight and wait for the back end to catch up to the front end. No offense, I have a bunch of custom fields already and no inclination to add one more. I appreciate the answer though! Saves me from trying a bunch of other combinations. -skye

well... that's close. I've been experimenting in Preview Sandbox since I figure I could use the practice. * I've managed to find out that the "DE:" part of the string is unnecessary (works either way, whether you have it on or not). * I've tried specifying name (project:Embedded Art Director:name) a...

nevermind, it looks like that's the case (project typeahead field does not show up as an option in a task report). Anthony: can you just swap out in textmode for any other project custom field and let us know if that works? e.g. here's what I get: valuefield=project:test custom field linkedname=proj...