This is the answer. In order to edit columns at all, the user's access level must allow Create access for filters/views/groups.

I've submitted this as a bug to Support for our instance. My case is 00423679. Since there was no mention in the release notes about deprecating an important feature, I'm hoping for a UI bug they can fix for us. My users are training to look there first before putting in help tickets to me to make m...

That all said, I got curious. A task report with this filter will show you all of the ones that were created, and the individual task CAN be deleted. You may have to monitor it for new tasks being created as people tinker with Priorities. I'm not sure when THAT specific task gets created, since my i...

When a new user account is created in Workfront, the system establishes a 'Personal' project behind the scenes for them automatically. (Or it does it the first time they create a personal task, I've never tested that far.) That is the project that houses items created as personal tasks, either via t...

In my instance, I have teams running in both options each for various functionality needs -  Kanban Team If:If you need a backlog functionality, with only approved (Ready) items making their way onto the Kanban board for the team to work onTeam is primarily given work via tasks/issues, especially if...

Funny enough, I can actually answer that one. The difference is in how the user moves the columns. If you grab the column itself in the grid and drag/drop it, that setting is not sticky just like it wouldn't be in a regular report. But if you use the 'Columns' menu, that setting change will stick. I...

After our first week of testing, I thought I'd share some of the questions and learnings that have come up from my team and see if anyone else has items they think the rest of the community should know as well. Old Personal Tasks - I had a worried user that turned out to be putting information into ...

Can confirm this was reverted (at least as of 10/16 when my instance went to the new home UI.) I had a ticket in my backlog to fix all of them, and found them working just fine when I went to make updates. 

Even though it's disabled in the waffle menu, I can still freely interact with it as this test user with a 'Request' license applied. 

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 ...