Enable @ Tagging During Workfront Request Creation

Problem Statement

In Workfront, users submit requests through the system and may need to coordinate with colleagues in other departments on the same request. Today, if a user wants another person to be engaged in the request conversation, the most common process is to wait until after the request is created and then manually add an @ mention in the Updates section.

This creates friction and can lead to communication occurring outside the request context—especially when users choose an easier workaround.

Current Workaround

After creating the request, users go to the Updates area and @ tag the relevant person.

However, many users find it easier to:

• open the email notification they received for the request, and
• forward that email to the teammate in the other department.

As a result, communication is no longer centralized in Workfront, and the “single source of truth” for the request is reduced.

Proposed Enhancement

Create a field type (or input capability) that allows users to @ tag/mention others during request submission—not only after submission in the Updates area.

Why This Matters / Business Impact

• Improves collaboration: Other department stakeholders can be notified immediately at the moment the request is created.
• Keeps communication centralized: Mentions would occur within the request itself, preserving context and reducing scattered updates across email.
• Reduces process friction: Users wouldn’t need to complete an extra step post-submission just to loop in collaborators.
• Increases visibility and accountability: Mentions help ensure the right people are engaged early and can respond directly within the Workfront workflow.

Outcome

Users should be able to specify who they need to collaborate with at submission time, ensuring that all communication stays in the request record and the right people receive the right context from the start.