What is going on with Workfront???

Unfortunately support is helpless to fix this stuff as it is based on faulty code, corrupt data, lack of QA, etc. The engineers are overwhelmed with trying to migrate data (probably the cause of most of these recent bugs) and keeping their heads above water and meanwhile your customers are struggling with the consequences of these bad decisions.

Saying "We're working on it" doesn't "pay the bills".

I think customers will remain unsatisfied until they see some actual fixes… if they're still customers by then.

Hi Ben - this is hard for me to read. See my feedback in bold. I appreciate your contribution regardless.

Hey All!

Thank you so much for participating in the community. I'm Ben Robbins, one of the Product Leads with Workfront and wanted to recognize that we've heard your feedback. We are always grateful to hear from our customers and their experiences with the Adobe Workfront . - Multiple WF team members have commented on this thread. We are aware you have 'heard' us. Please tell us what you are doing with this information. It's not a matter of 'hearing' us it's a matter of what you are doing with this information.

With the transition to the New Workfront Experience we have moved carefully to ensure the optimal experience for our customers. To create a future ready and quality experience, some tough choices had to be made and not every functionality was migrated nor will every feature work at complete parity with classic. These decisions are generating favorable results. - The NWE has been rolled out for almost two years or so. We were instructed to bring our team members over NOW because Classic would be going away. This was encouraged despite the degradation of performance customers have detailed.

From a performance perspective we’ve seen improvement in the overall operation of the New Workfront experience. One highlight to call out would be a 32% year over year performance increase in the top 25 most visited pages by our customers. We're coupling those improvements by monitoring customer reported experience around tasks and lists. - What performance metrics are you measuring this again? Is it 32% over all users, just certain pages, just certain parts of the program, etc.? Providing this metric seems like a red herring without any insight into what this information is referencing.

We welcome opportunities to discuss your experience in further depth so please reach out to your customer success manager or support for further dialogue. - This part in particular is challenging to me. Is there a SLA on when you expect an item to be resolved with a customer calls you? For instance, is more than 3+ calls about the same issue, more than 6+ calls, more than 10 emails feel like a sufficient use of time by your customers? Is there a SLA for an expectation of when or how long a problem should exist before it's an escalation? I don't submit tickets any more because frankly spending call after call after call is not productive.

We've had three? four? "Customer Success Managers' in the past three years. Our last I did not even get notice left the company so I reached out to their boss and she ALSO left the company.

I know some of these things can be accounted to 'growing pains' and I am not one for being negative nelly. However, it seems the community is the only true way to get anything acted upon.

You may not have intended your response to be but it came across as very patronizing without providing any real specific instances of addressing the issues.

Here's an example: note the dates.

With all due respect @Benjamin Robbins - inactive‚ , that doesn't help. I believe you're addressing the wrong issue in this particular thread.

If by "tough choices" you mean making filters work intermittently, disallowing the deletion of old deprecated forms, showing filters in menus that were deleted long ago, showing partial screen redraws with large blank spaces, constant white screens, I think you get the picture, then I think you should re-think those choices. And if those were conscious choices, that will make your customers even more angry.

Reaching out to support has done zero for performance, and has become a bit insulting to be told over and again "look how much faster we're making it, you should pat us on the back and be grateful".

And as for your "performance increases", you can't slow it down by 70% and then speed it up 10% and call that a performance increase, we're not stupid.

This thread is about a plethora of Workfront glitches, bugs, and white screens that have increased ten-fold in the past 2 or 3 weeks that undermine trust in Workfront's ability to deliver a reliable, working product.

Workfront is not cheap and I think we all deserve more than your above "prepared statement" that really says nothing.

Hey All!

Thank you so much for participating in the community. I'm Ben Robbins, one of the Product Leads with Workfront and wanted to recognize that we've heard your feedback. We are always grateful to hear from our customers and their experiences with the Adobe Workfront .

With the transition to the New Workfront Experience we have moved carefully to ensure the optimal experience for our customers. To create a future ready and quality experience, some tough choices had to be made and not every functionality was migrated nor will every feature work at complete parity with classic. These decisions are generating favorable results.

From a performance perspective we’ve seen improvement in the overall operation of the New Workfront experience. One highlight to call out would be a 32% year over year performance increase in the top 25 most visited pages by our customers. We're coupling those improvements by monitoring customer reported experience around tasks and lists.

We welcome opportunities to discuss your experience in further depth so please reach out to your customer success manager or support for further dialogue.

Yup, irritating and annoying. Have asked my AE and ASE what is going on and only get vague 'migration' issues... (to another server)

Today is just the icing on the Workfront blunder cake. Everything is down for everyone.

Half of our Global team has freeze on Workfront in Chrome environment today - blank screens for our team. I have just raised a critical ticket with Workfront. Agree with all points above very buggy at the moment especially working with Resourcing very slow to load - waiting minutes for load on these filters.

Adding in my bugs to the list:

• Search feature rarely works correctly ‚Äì created a specific report for that purpose
• Slowness with data loading (slow compared to comparable testing in classic at the same time). Forms are especially slow (there is a 500 field max and we are just over a 100.... I'd hate to see if we had closer to 500 on a form).
• Screens don't automatically load or update. I find myself having to constantly refresh my browser window to get contents to update. I didn't have to do this in classic.
• On occasion, I just get a completely white screen with no data loaded. I have to hit refresh to make something pop up.
• Text mode in reporting no longer functions ‚Äì defined widths are now being ignored, leading to the decreased use of reports.
• Features intended only for system admins ‚Äì like Blueprints availability ‚Äì are showing as an option for our read and review only license users causing confusion.
• Overall system degradation - we have instructed our users to stop using Google Chrome (the default) and start using MS Edge because quite frankly WF doesn't play well in Chrome anymore.
• Last line of every project is being cut off so you cannot read it.
• Oh and not as related - I still cannot search the community because of these loading errors anytime I access the site.
• 

Hey everyone,

We hear you loud and clear! We want to assure you all that we're working through all open support cases and are committed to seeing each of them through to resolution. Please continue to work with our Support teams when you encounter problems in the system so we can work through those problems and get them resolved as quickly as possible.

I worked with our management team and we've gone through all the cases that have been mentioned, as well as some that haven't, and we're happy to confirm that we've either already addressed, or are in the process of addressing the issues mentioned.

I also want to take a moment to remind everyone that we post our known issues here: https://one.workfront.com/s/article/Known-Issues

Thank you all for participating in our community.. you folks are a shining example of what it means to *be* a community!

-Dustin Martin

Adobe Workfront Assigned Support Engineer