We have multiple instances and past efforts to merge them have not been successful because of different business functions that the instances meet. We do, however, have an important need to share data, especially for corporate-level projects or initiatives. Bringing in a 3rd-party tool is problemati...

Yes, and then I get a dire warning about the impacts of not setting the new user as a Sys Admin.

It should be clear that this is bigger than LEAP (now we are getting adds for the LEAP in London, which is no better). Workfront should not be using the welcome page as an add. It is inappropriate and cheapens the tool.

I would also like the "Clear all predecessors" checkbox to be unchecked by default. I copy many sets of tasks (parent with children) and have to remember to uncheck that box or the dependencies are lost. I've had a new PM literally have to re-do hundreds of tasks because she forgot to uncheck the bo...

Thought it may be useful to point out something that I discovered accidentally and may not be widely known: If you display a list of objects with a view that contains custom field attached to a custom form in the view, if you add content to the field, then Workfront automatically adds the necessary ...

At the risk of drawing out a topic unnecessarily, but I'm concerned that what appears to be a simple topic can be more complex than thought. Our large organization evolved with multiple instances (8, with around 1100 users) and have made several attempts to combine, so I talk from that practical exp...

Yes, it is true that there must be a strong division of labor, function, or purpose between instances and for the most part this is true in our organization (but may not be true in others). There are some activities where a functional overlap exists and the decision has been made that a few PMs have...

We have multiple instances of Workfront in our organization (some with hundreds of users and others not so many) and have found that approach to be beneficial to us. The benefits of different instances relate to being able to make the user experience less confusing. Many objects within the instance ...

Lucas, Thanks for your response. I can see we both have some interesting stories about silly “works as designed” responses and have experienced similar situations. Let’s hope that things have improved and will continueto do so. Regarding your WBS suggestion that is a great idea...

I too have been a long term user of AtTask/Workfront and have had the same frustrations with Features requests, i.e., lack of visibility and responsiveness. To that, I would add the frustration of being asked to submit Feature Requests for what I see are bugs. Since I help run a help desk (in Workfr...