Um... NO! | Community
Skip to main content
RandyRoberts
Community Advisor
Community Advisor
October 16, 2024
Solved

Um... NO!

  • October 16, 2024
  • 4 replies
  • 1827 views

Priorities is nether simplified nor will it help MY users organise their work. I thought it was lesson learned from the blueprints menu item everyone complained about.

 

Best answer by KatherineLa

UGH! I had specifically asked WF Support a few days ago, if I disabled "Priorities", will users see it in the waffle menu, and they said users would not see it in their waffle menu AND they also confirmed users would not see it in New Home. Guess it is just yet another communication that I need to send to my users to 'please ignore', which I should not have to do in the first place, as I opted to disable it. Again this is just adding more clutter and confusion for my users.   


Also adding, not only will they see the option even if it is disabled, the 'Request' license type completely ignores the setting entirely. Anyone in my instance with Request license type is able to interact with the Priorities feature freely even though it is disabled in Setup. Including being able to add tasks and issues to any project they can see, which is NOT something they're allowed to do under that license type. The task/issue does not actually get added to the project, but the user receives a success message saying that it has been added.

 

My case number on the security hole is 00422817 if anyone else sees this behavior and wants to add on. 

4 replies

October 16, 2024

Hi Randy, did you disable "Priorities" under System --> Preferences and it is still showing up in the Waffle menu? 

RandyRoberts
Community Advisor
Community Advisor
October 16, 2024

yup, that's why it says ask your admin..." I'm guessing trying to get my users to pressure me into enabling it, which isn't going to happen.

KatherineLaCommunity AdvisorAccepted solution
Community Advisor
October 16, 2024

UGH! I had specifically asked WF Support a few days ago, if I disabled "Priorities", will users see it in the waffle menu, and they said users would not see it in their waffle menu AND they also confirmed users would not see it in New Home. Guess it is just yet another communication that I need to send to my users to 'please ignore', which I should not have to do in the first place, as I opted to disable it. Again this is just adding more clutter and confusion for my users.   


Also adding, not only will they see the option even if it is disabled, the 'Request' license type completely ignores the setting entirely. Anyone in my instance with Request license type is able to interact with the Priorities feature freely even though it is disabled in Setup. Including being able to add tasks and issues to any project they can see, which is NOT something they're allowed to do under that license type. The task/issue does not actually get added to the project, but the user receives a success message saying that it has been added.

 

My case number on the security hole is 00422817 if anyone else sees this behavior and wants to add on. 

-JC
Level 5
October 17, 2024
JustinRenteria2
Level 6
October 17, 2024

I really dont understand why Workfront is forcing this untested functionality onto our users. This decision does not seem like it was thought through completely. Additionally, I reviewed the release notes with our change mgmt team a couple weeks ago in preparation for the release and this functionality was not listed. There should be a longer period of time to review new functionality like this before it goes live. 

kautuk_sahni
Community Manager
Community Manager
July 16, 2025

@randyroberts Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!

Kautuk Sahni
RandyRoberts
Community Advisor
Community Advisor
September 1, 2025

No, the problem is not solved. Adobe thinks they know what my users want more than I do and they're OK with cluttering up their menus with useless junk to try to pressure me to enable it. So now I have 86,000 (NOT a typo) users with something in their menu that they won't use and I can't hide it. It's really a loss of governance for admins.