Tagging Other Tasks?

[ChrisFl]

My organization is still getting used to Workfront and beginning to discover some of the more advanced functionality. We really like the ability to tag users, but is there a similiar way to tag other tasks? For example, my dev has task 456, but I want to make him aware of a change in task 123 that impacts him. I have been copying the tasks URL for now, but it seems messy. Is there a way I can tag 123 within a comment of 456? Chris Flynn FHCP

[VicAl]

I don't know of a way to tag the Task, but you can tag the assignee of 123 in the comment of 456 (as I think you are doing). You can also do a bulk comment if you select both 123 and 456 and hit Edit > Comment you can bulk edit the comment, then both tasks get the same comment and you can tag people on that bulk comment as well (just know they'll get an email for each task – so they'll get two). Other than that, I can't think of anything else. Vic Alejandro, PMP, CSM | IT Program Manager Denver Water | t: (303-628-7262) | c: (303-319-6473) "http://www.denverwater.org/"> http://www.denverwater.org INTEGRITY | VISION | PASSION | EXCELLENCE | RESPECT

[kareng30607741]

Another feature you may be interested in is the ability to subscribe to projects, tasks, and issues. When you subscribe to a work item, say a task, you receive an email and/or an in-app notification letting you know when a comment or an update is made on the task. So, even though you are not assigned to the task, you can still keep up-to-date on the work being done on the task. You can learn more about subscriptions in the article "https://support.workfront.com/hc/en-us/articles/115000097553" "Subscribing to Items in Workfront." Karen Grant Workfront

[ChrisFl]

Thanks for the input. I'm in a situation where I've had a requirement change and I'm updating the requirement ticket 123, but I'm trying to alert the dev assigned to ticket 456 to check ticket 123. Being able to tag 123 in 456 (ie, "Dev see changes in 123 for this task") would be nice and similar to how we used to reference tasks in Jira, which is why I asked. I'll just keep using the long links for now. Chris Flynn FHCP

[EXP_-_DustinMa]

Hey Chris, Because of the dynamics of Workfront with how tasks work, #123 may change throughout the project life cycle, and may no longer be #123 in the future. Something I'd suggest, is to continue linking, or if it's a big impact, add the URL to the task in the other task's URL box under Task Details, as seen below: https://cl.ly/3c3E3F3Q0B1Z That way it doesn't matter what task # is in the list, but instead you can focus on having easy access to the other task without having to rely on a #. I hope this helps! Thanks, Dustin Martin Tier 2 Assigned Support Engineer Workfront