On Hold Status that removes work from My Work

[#1]

We would like an "On Hold" Status that removes work from My Work but doesn't cause the request to be complete. The status should remove project work from Working On and change the request status to On Hold as well. Then, when the project is set to current again, the request should return to In Progress.

[#2]

We have considered using the work around offered in the help article Project goes "On Hold", Tasks still show My Work List (link: https://support.workfront.com/hc/en-us/articles/218455578-Project-goes-On-Hold-Tasks-still-show-in-M...). From my point of view, this work around could be eliminated with implementation of this idea.

However, we have been unable to find a work around when we need to set a status of On Hold on our tasks and issues which is a pain point for our users. Thus, I am recommending that as a part of this idea that the following also be included:

(a) set the status on a Task to a status of On Hold which equates to a value that would remove the task from My Work.

(b) have the equates with value of On Hold for issue statuses to remove the issue from My Work

When the object (project, task or issue) is set to a status which equates with On Hold, planned completion date shouldn't require a user to regularly update but rather be automatically adjusted to a date in the future until the status changes to a value such as Reopened, New, In Progress, etc.

[#3]

Love your enhancements, Heather!

[#4]

I agree with Heather. Those are good extra enhancements.

Also, the workaround presented in https://support.workfront.com/hc/en-us/articles/218455578-Project-goes-On-Hold-Tasks-still-show-in-M... doesn't work for us. It suggests making a new custom status for "On Hold" that's the equivalent of "Dead".

Unfortunately, we generally create our projects from requests, and tie the resolution of the original request to the project.

We find that when you mark a project as Dead (or Dead equivalent), it changes the original request as Resolved. Which, if you're putting the project "On Hold" (as a Dead equivalent), you don't want the request to be "resolved". Especially because our configuration sends a notification.

It's on hold, because the request has yet to be resolved. (In my tests, when you change the project back to "Current", the original request stays as "Resolved"...it doesn't go back to "In Progress").

As a workaround, I make the custom "On Hold" status an equivalent to "Planning" instead of dead. It achieves similar goals to this workaround, but it doesn't mark the original request as "Resolved".

But ultimately, I think a better solution would be to make the default On Hold status remove tasks from the "My Work" area, rather than making a custom status workaround.

[#5]

I'd like to add to this. If a project is marked On Hold or Dead, both tasks and approval requests should be removed from the "My Work" or new "Home" list.

[#6]

This is exactly what our team needs as well! We have multiple deliverables in our projects, and some need to be put on hold so that they don't show up in users' work lists. One addition: I would like to be able to create multiple task statuses that equate with on hold.

For example, we would use "On Hold" to show that a deliverable is temporarily suspended in cases where we don't have enough info to proceed, need to strategically evaluate, etc. We would also create another task status called "Idea" that equates with the on hold task status functionally, but gives us a different status to pull reports on. This essentially becomes our backlog of nice-to-haves that we could pick up when the team has some open time to fill. (We're not a fully Agile team operationally, so it doesn't work for us to use the Workfront backlog/iterations. But this status would let us essentially create a backlog for us to refer to without having to set up our teams as Agile in the system.) I would also probably create a third "Planning" task status that equates with the task On Hold status functionality, so that I can be setting up a new deliverable in the project without having to put the whole project into Planning status while I gather information and build it out.