What is going on with Workfront???

[amyb35793975]

Is it just me or is Workfront extra whack lately? I'm submitting support tickets CONSTANTLY ...

[KathyPal]

I don't necessarily agree this is a 'New Experience' issue since we had no problems until the Adobe merge and I wonder if it's migration issues.

[RandyRoberts]

While you are correct in that assessment, this is just the latest round of failures. There were existing problems with NWE for the past year or 2 (white screens, multiple refreshes required, partial screen redraws, etc.) that have not been resolved and this latest round of issues is layered on top of that. This compounds the frustration and buyers remorse a lot of us are feeling right now.

Workfront reliability was already precarious since NWE and now with the data (and probably code) migration, it takes reliability to a new even lower low.

[Kelly_Wehrmann]

Have to agree with you @Randy Roberts‚ ...

When this new UI rolled out a couple of years ago, there were a lot of issues with the UI (you mentioned above), which is why we never migrated until now. I was hoping a lot of this would have been cleaned up before we made the move, but not such luck. With the plug being pulled on Classic in July, we've been forced to migrate. We have everyone migrated, its just sad to see some of the same issues still around after this much time has gone by.

Today I attempted to add 5 new tasks to a project via inline add task functionality. The first 3 seemed ok, but the last 2 weren't. The font on the last 2 appeared "gray" for a while like they system was still trying to process the add request. After several minutes they didn't change. I refreshed my browser window (because it seems like you have to do this constantly in the new UI) and neither of them appeared in the task last at all. So I went ahead and added them again. These 2 added with no problem. I refreshed my browser window again and all of the sudden the other 2 (that I thought failed) were now visible. Not sure where they had gone or why it took them so long to show up. Just had to shake my head and keep working. I had no screenshots, so no point in opening a support ticket, plus I've spent more time on tickets the last few weeks than I should be.

[KevinJe]

I completely agree. We did exactly the same thing. We migrated our whole user base over about a month ago because we waited as close as possible to the very end before pulling the plug on Classic. Same reasoning as you (hoping all of these issues would have been resolved or they had it all together finally). Only to find out that isn't the case, thus resulting in myself and our other admin having many requests coming in from users about functionality and UI problems.😐

[CalvinFold]

Having been through exercise like this in the past, we did the opposite. As soon as we knew they had firm dates to deprecate Classic, we decided to move over sooner rather than later so we could start learning the differences and changes. We did a test group at first, refined a bit, then moved everyone elses.

Granted, we may have a smaller number of users than many of you and that certainly plays into the decision.

[laurence_jayawardane]

We are seeing similar issues here also...

[Christina_Jarosz]

Today's embarrassing issue - we recently have went through a company wide rebrand. When the brand launched 05/02 we made a full branding update throughout Workfront.

Today I'm getting alerts that our Corporate marketing team is seeing our OLD branding - and old logos. Our executive management is irritated.

Branding is system wide - not by template, user, etc. It's all or nothing for everyone. Submitting a ticket but anyone have any suggestions? Yes, cleared our caches etc.

[RandyRoberts]

I see a bunch of old filters from Classic that were deleted long ago when I'm sharing filters. I've also recently seen teams in a project list and projects in a tasks list, etc.

It should be emabarrassing but I don't think they're embarrassed at all. I'm embarrassed because it reflects poorly on me for defending Workfront everytime corporate questions it's value… no longer.

[Christina_Jarosz]

FYI - Another notable issue. In setting up a new user, we always always ALWAYS require SSO.

Editing the user later in the day I see that the SSO requirement has been toggled off and is now not part of the SSO.

Submitted a ticket.

[puhoneya]

My system admins and I were so relieved to see this thread when it popped up. When I reached out to our WF account executive on May 11 saying "I don't know what Adobe is doing to the solution I used to love but this is becoming untenable" we were told we were the only ones that had reported having any kind of problems. I was at my wit's end as basic settings (task statuses and task status defaults) were no longer working properly, I could no longer edit reports that I had created a few years ago without the logic breaking, etc. We were told it was a "speed" issue on our end (uh, really????), advised to stop trying to edit old reports, told to rebuild complex reports (that were constructed with custom text mode additions), etc. It was very frustrating and angry making. We were told -- as if we were newbies who didn't know what we were talking about -- to "take advantage" of "inexpensive" ($250/hour) paid help hours to troubleshoot our problems (!!!) when those are useless when you have functionality issues. I personally was fine with the temporary slowdown issues we had when we migrated from Classic to NWE (seemed like they miscalculated a server load -- not great, but it did improve over time), but this is something bigger -- I think this "culling" of functionality is really just awful, and I blame Adobe. I also think their "Summit" was a complete joke; didn't learn a thing. Was finally hoping to make it to a live LEAP after all these years. I also think that this whole idea of just getting rid of the "lesser used" features really is insulting to people like us who chose WF because it was very close to an enterprise solution and promised to be able to fulfill all our custom needs. Bah.

[CalvinFold]

I attended my first "LEAP" as the virtual version during the pandemic (was free, company wouldn't pay to send me to the Live ones), but that was also just after Adobe took over. I was very, VERY disappointed at the heavy-handed Adobe presence and wasting time in each seminar hawking Adobe products and integrations. I heard the live ones were fun and had a great sense of comraderie. Shame I missed those days.

Then, Adobe absorbed the Lion awards into the Adobe-wide awards, diluting the ability of Workfront-only users to really have a crack at them and making Workfront's community feel less special…just another cog in the great Adobe machine.

I didn't attend the conference this year…I assumed it would be more of the same. I get more out of the Community here.

What's really annoying is I dislike Adobe, not the WF devs. I've been working with the Beta devs, talked to folks on the Armenian teams, and they all seem like good, enthusiastic folks who really want to make a good product. I can only assume somewhere in their upper management chain is where it is going awry.

Adobe has a bad case of "Aldus Syndrome" (had it for a while now)…and the only cure might be for an upstart to knock them down a peg…or steamroll them over.

Yes Adobe, I remember how you came to prominence…and you have become what you once fought against. Shame really.

[Christina_Jarosz]

I value this feedback. I despise being negative - so I do try to be constructive in my comments. However, the WF that 'once was' no longer exists. Adobe has swallowed it, chewed it up, and spit it out. I'm not sure I agree with their strategy of absorbing WF vs. allowing it to continue to exist as a standalone product (i.e. Workfront, an Adobe Company).

We have users that are interested in implementing WF further in their area and I have put them on hold for now. I don't feel confident championing a product that no longer is considered a champion in itself.

To that end, has anyone developed an exit strategy to reduce their dependency on Workfront?

ETA: I do applaud that they are letting this thread stand in the interest of transparency. I'm not sure if they intended it to be publicly visible since it's a public site indexed by google searches.

[Kelly_Wehrmann]

**** UPDATE to the below Post *****

Tracy from Workfront reached out regarding my post below and helped trace this through.

In this particular instance, he was able to verify that the email in question was sent to the Workfront System Admin Id that we use for a few API processes, not a actual named user.

I continued the trace on our side and received confirmation that our email system intercepted the email and routed it to a Distribution List (DL) associated with this particular Workfront System Admin Id. This DL is the reason why this email found its way to resources that were not setup as Workfront System Admin. :)

**************************************

Has anyone else had reports from non-system admin users in their instance about receiving a Workfront Announcement today (Complete the transition to the new Workfront Experience)?

We have just completed migrating of our ACTIVE users, but have not officially pulled the plug on Classic. We did this intentionally, because it gives us (system admin) the opportunity to compare/contrast issues reported in the new UI to Classic.

As you can imagine, this email has created confusion for our users because they 'thought' they were already migrated.... now they receive an email like this?!

This email should have NEVER gone out to non-system admin users. I can't even come up with a good reason why they would have sent this out.... it makes no sense!

I've reached our to our CSM and Renewal Specialist to let them know this happened and to find out why. If it was a mistake they should have sent another message letting people know to disregard it. I'm disappointed that they did this and very disappointed with communication for other things like this, especially lately.

[RandyRoberts]

I honestly feel as though Workfront is not the better solution for my organisation any longer. When renewal comes around, I will not be supporting a piece of buggy, unreliable software like Workfront. I will suggest we switch.

[Christina_Jarosz]

Today's issue - requests being submitted through request queue and no request form attaching to the request.

The form shows as NOT attached but the updates show that it was filled out (shows the answers).

Submitting a ticket.

[EmberLynn]

I want to add to this since I have not been able to find any discussions about it and was wondering if others are having the same problem.

Setting the status for an issue or request has been a challenge for some of our users. When clicked, the status dropdown only sometimes displays the list of available statuses that the user can set. Other times it only renders one or two selections. This appears to happen at random regardless of the issue or who is trying to set the status. One hour the dropdown will only render half the list, the next (on the very same issue) it will render the entire list.

[Christina_Jarosz]

UGH! Today's issue:

We are getting this error in EVERY SINGLE COMMENT and does not confirm comment completion.

[Christina_Jarosz]

More errors.

[Christina_Jarosz]

No time was attempted to be entered...

[Christina_Jarosz]

And trying to find out why something is not working....on the Adobe support page...

[JohnOS1]

We were immune to most of the weirdness going on with Workfront proper. (Proof and the Proof API, on the other hand...)

Yesterday, when attempting to edit text mode in a report, we got an error saying that we weren't allowed to.

We were literally able to do so all but 15 minutes earlier and we did the whole "Have you tried zapping your cookies and cache" solution as well.