I believe this is related to using the external page link at the bottom of the dashboard builder to essentially embed a Workfront dashboard within another Workfront dashboard.

Depending on the number of fields on your custom form (and the logic on those fields), as Madalyn mentioned a View might be your best option since there's no way to edit what shows in that New Task window that pops up when creating a new task. Instead of having users click the New Task button at the...

This would be great! I've avoided defaulted values in custom fields for this very reason.

Hi @Madalyn_Destafney  +5d would give you the 5 workings days, predecessors should ignore non-working days (per the schedule attached to the project or the user depending on which you have set to use). But I don't believe there's any way to tell Workfront to set it to 5 days after another certain da...

We were having a ton of issues with the +addressing, the +addresses were being auto-added to users in Proof who had a profile in another instance of Proof with that same email. So corporate was not letting those notification emails through.  I believe - don't quote me 100% on this, but I believe Wor...

Sorry if you've already tried this, but have you had them clear both cache and cookies (or had them do "the Heather" as my former team calls it! LOL)? Generally that's the first thing I have users try if they aren't seeing the same thing I see when I log in as them - and the first thing support will...

@kswaringen  I'm wondering if the user where these tasks are still showing clicked Work on It for those tasks before the project was terminated...?   I know when we change a project status to On Hold any tasks where the user has started working on them, those tasks stay on Home. I haven't checked to...

Hi @Madalyn_Destafney, congrats on the new gig, I also just started a new gig! For the last couple of admins that left my old instance, I did go ahead and make new calendars for any they created - if those had been shared with users. But for all the stuff I created I did suggest they leave me in the...

Good call out @Doug_Den_Hoed__AtAppStore having both a native and custom field with the same name makes for a reporting nightmare - and reporting includes creating any filter/view/grouping on any list, not just strictly in the reporting area. You don't know which field to pull into your report when ...

Another feature I'd like to see related to this is if you create a custom field with exact same name as a native field, you'd receive at the very least a warning, preferably not be allowed to create a custom field with that same name.