Expand my Community achievements bar.

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

Comments from Request to Converted Project

Avatar

Level 2

Hello,

 

In our organization, we have a team who needs to get requestors updates in the issue which is converted to a project and users from the project should be able to communicate back to the requestor. As of now, we are seeing that comments made in the request after its converted to project is not appearing in the project. Vice-versa, project updates do not relay back to the requestor. Can someone help on how we can resolve this?

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

What about taking a creative approach with layout templates? As noted below, your use case is functioning how it is expected to in Workfront. However, you could give requestors access to the projects, but reduce their layout template for Projects to only show the updates tab on the project - maybe even project details (but hide tasks, etc.).

 

Then, on access levels, if they shouldn't see every comment, restrict their access to only show comments where they are tagged.

 

Just some additional considerations if you don't have options for Fusion, etc.

View solution in original post

5 Replies

Avatar

Community Advisor

@shirinshaikh - this is expected behavior inside of Workfront. After conversion the request and project do not speak to each other. Requesters and project owners should use the converted project for all communications after it's creation. 




Avatar

Level 2

Hi @KellieGardner - For our requirement, we do not want to give the requestor direct access to the project or communication will become confusing. Requestors won't know if they are updating in the project or the request. Is there a way to workaround this?

Avatar

Community Advisor

You might be able to accomplish something with Workfront Fusion if you have that but natively in Workfront they are considered different objects so it won't be a option.




Avatar

Level 7

Once requests have been converted to projects everything should live in the project, you can't go back to the request, any info updated in the request will stay in the request (issue) and not be visible in the project.  The only realistic option is to update the live project.  For your needs, is this communication going to be done inside of Workfront or outside?

In my Workfront instance we have a ton of requesters who do not have the permission required to update live projects, for any project changes the requester would need to contact the owner or coordinator for changes to be communicated.

Avatar

Correct answer by
Community Advisor

What about taking a creative approach with layout templates? As noted below, your use case is functioning how it is expected to in Workfront. However, you could give requestors access to the projects, but reduce their layout template for Projects to only show the updates tab on the project - maybe even project details (but hide tasks, etc.).

 

Then, on access levels, if they shouldn't see every comment, restrict their access to only show comments where they are tagged.

 

Just some additional considerations if you don't have options for Fusion, etc.