Hi Lars,   I'm not aware of any issues. However, I recently got caught out with summary panel customisations not behaving how I expected. . . . .   For any task UI customisations to take effect, the person who is assigned to the layout template must also be assigned to the task where they are using ...

Hi,   Assuming that the date field is being captured on a project custom form (as your text mode suggests), you shouldn't need to use text mode at all. The Project object and it's data attributes are all available natively from a Document report. In the report builder, simply add a column and search...

Hi,   This isn't possible to do via a calculated field. An issue is classed as a collection at the project level (since a project can have multiple issues). There is no way for a calculated field to establish which issue to pull the data from.   The only way to carry data from an issue to the projec...

Hi,   You can set up a folder structure on your project templates. When you convert the issue to a project using a given template, the folder structure on the template will be automatically applied to the project.   It's not possible natively to have a folder structure automatically applied to the i...

Hi,   Give the following a try:   IF(ISBLANK({DE:First Update Timestamp}),IF({lastUpdatedByID}!="ID OF FUSION ACCOUNT" $$NOW,{DE:First Update Timestamp}),{DE:First Update Timestamp})   In plain English, what is calculation is saying is; If DE:First Update Timestamp is blank then check that the ID of...

Hi,   Sounds like an ideal use case for Workfront Planning . . . .   Take a look at some of these resources:   https://business.adobe.com/uk/blog/the-latest/introducing-workfront-planning-building-and-activating-your-marketing-system-of-record   https://experienceleague.adobe.com/en/docs/workfront/u...

Hi,   You can find all of the details of upcoming and previous Workfront product releases here.   It's unlikley however, that a recent release would cause differences in UI between you and your colleague. This is more likely to be a difference in UI settings between you both (either a user specific ...

Hi,   Instead of using a "contains" filter modifier, I suggest trying a "like" or "cilike" modifier. Like modifiers work similarly to contains modifiers, but they enable you to insert wildcard characters to break up the text. So your filter would look something like this in text mode:   name=%sr%nam...

Hey,   That's strange, it works in my instance.   Can you make sure that there is a Tab character inbetween "CUR" and "PLN"? Tab characters don't copy over from experience league into Workfront, so if you've done a straight copy and paste of my code this might be the problem.   Best Regards, Rich  

Hey,   Looks like you are nearly there. Since you are filtering one field against another, you need to tell Workfront you are doing this by adding "FIELD:" to your filter criteria. So "assignedToID=project:ownerID" will become "assignedToID=FIELD:project:ownerID"   assignedToID=FIELD:project:ownerID...