Expand my Community achievements bar.

The next phase for Workfront Community ideas is coming soon. Learn all about it in our blog!

New Experience - Show Task/Issue Description on the same page as Updates

Avatar

Level 3

4/9/21

In the New Workfront Experience, the Task/Issue Description is on a separate tab than the Updates, making it not possible to see the task/issue description when making an update.


Use Case:

A user reports an issue through Workfront and in detail describes their issue or asks questions in the Issue description field.

That issue is then routed to our IT Team who will triage the ticket. This team will likely be adding documents to the ticket and thus will navigate to that Issue page (since they cannot add documents from the Home page).

First, the Updates tab looks so empty without a description - Like I'm on this page, what do I do?

Second, to see the description of that issue, the user has to click on the Details tab to see the description (plus a lot of other things).

I think it would be very helpful to add the task/issue description to the updates tab so that users don't have to toggle between the 2 tabs and just for ease of use.


P.S. If you didn't catch it, we would use the same workflow for making updates to tasks and thus need the task description on the updates page as well.

5 Comments

Avatar

Level 4

4/23/21

That is one of our main pain points within the NWE!

I am a huge advocate of Workfront within our company. But solutions such as the separation of description and update stream - which simply doesn't make sense from a usability point of view - make it difficult for me to hold up the flag for Workfront.


I also cannot understand why the description is so neglected compared to the update stream and why rich text and formatting are still not possible here.


We have numerous developers who “have to” work with Workfront and I'm tired of hearing how well other systems (e.g. Jira, GitLab) do justice to their ideas.


Avatar

Level 2

2/7/22

This is the #1 requested functionality by our organization's users as we've started adopting the new interface.


Not being able to see the description when making an update is the major pain point I hear about. It's the one that users are most frustrated by and vocal about. This is an area of the new interface that is making us slower. When reviewing and triaging incoming work, users can't see pertinent info and make an update at the same time. This affects most of our users on a day-to-day basis and makes doing their jobs harder.


I'd love to hear that WF is going to address this before migrating additional users to the new UI. Why would I proactively move users to a new interface that is going to frustrate end-users and make a daily task less efficient?