Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Workfront Experience - Bad column controls in projects

Avatar

Level 6
This is a preexisting issue and I thought it was going to be fixed in the New Experience, but it looks to still be problematic. Feedback is for columns shown in the task tab of a project Issue 1 - Resizing columns pushes stuff off the end of the screen. If you manually shrink a column it make the last column wider to keep the screen filled. If you then widen the column again, the new wider width of the last column pushes off the end of the screen. Issue 2 - Manually resizing columns widths permanently breaks the programed widths of a view (usewidths=true, width=150). The browser cookies get locked in for the manual set widths and forever-override the view settings. Can be recovered by clearing all cookies, but this is tedious and non-intuitive. Issue 3 - Column widths are driven by cookies after (if you ever click on a column header causing it to override the view's width settings) so width performance is inconsistent from browser to browser. Issue 4 - It is essentially impossible to print out a project plan with the width chaos. We have corporately given up on printing out projects for huddles or stand-ups.... but it always worked fine before "full screen" views came out. Matt Marks
2 Replies

Avatar

Level 10
One of the other issues our users have is that after they have resized columns to make them wider, each time they refresh the page (or navigate back to it), the columns get gradually narrower and narrower until they have to resize them again. For users who have a lot of activity, they are resizing the same columns several times a day. This is an open issue with Support at the moment... David Cornwell

Avatar

Level 6
That is good to know. I haven't noticed this yet, but we do have recurring complaints of messed up columns and this might be the cause! Matt Marks