Expand my Community achievements bar.

Don’t miss the Workfront AMA: System Smarts & Strategic Starts! Ask your questions about keeping Workfront running smoothly, planning enhancements, reporting, or adoption, and get practical insights from Adobe experts.
SOLVED

Updates from Requests are not Carrying over to Projects when Converted

Avatar

Level 1

Hi all, 

 

Is anyone experiencing this issue?

 

Updates are not carrying over to the project when converted?

Topics

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

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Based on documentation, this should copy over when converting issues to projects. 

 

  • Issue comments are also copied to the task or project converted from the issue, but tagged users will not transfer.

 

Overview of converting issues in Adobe Workfront | Adobe Workfront

 

Might be worth a support ticket as it sounds like it's a bug. 




View solution in original post

6 Replies

Avatar

Correct answer by
Community Advisor

Based on documentation, this should copy over when converting issues to projects. 

 

  • Issue comments are also copied to the task or project converted from the issue, but tagged users will not transfer.

 

Overview of converting issues in Adobe Workfront | Adobe Workfront

 

Might be worth a support ticket as it sounds like it's a bug. 




Avatar

Community Advisor

Learn something new every day! Thank you for the link, Kellie.

Avatar

Level 7

I don't know if your issue is related to mine but my comments are showing up ~1 hour late on the project. When we caught this issue, it was semi-related to our scenario that converts issues to projects.

Phantom Note Updates 

Avatar

Community Advisor

@Lawson02 @MargretteBoyer  - did the issue get resolved?

Avatar

Level 7

Nope, seems to be a problem with updates being delayed when they are created in the API. Support says that they are working on it but don't have any current updates.

Avatar

Level 1

Yes, it was a bug