Add an update to the update feed and have a link in project and request header area when requests are converted to projects.

[#1]

We would like to see an update in the update feed along with a link in the header of the project and request when requests are converted to projects. I have added screenshot examples below:

[#2]

I was just getting ready to submit the idea to have the custom form from the original request appear in the custom form tab underneath project or task details (when converting the request/issue into a task or project). This suggestion is MUCH better. Staff find it frustrating to navigate to the Overview tab and then scroll down to the bottom for "Resolved By". They are accustomed to seeing what they need most of the time in the Custom Form tab. This is a great idea!

[#3]

Also - restrict any additional comments/work on the original issue. Many times, the original assignee on the issue isn't the one managing the project nor are they the one working a task within the project.

[#4]

I think this information could be added to the pane on the right side of the screen, or somewhere in the main ticket window. Lots of people just don't navigate the other tabs so it would be easier to just have the information right there.

[#5]

Gabriela, the problem with that is that the pane on issues on the right side hides on some views and projects don't have a pane so it would be a little inconsistent as well. If it shows on the issue/project header, it is visible no matter what tab you are on. Having it in the update feed would just be a nice extra so you could see who did it and when it happens.

[#6]

I agree with Heather as an additional request for this. This is a big problem for us where people go back and change the something in the request but it's already been converted and that info doesn't get transferred over. I'm a broken record telling our users (particularly our client services team that puts in a majority of the requests) not to update custom forms and leave status updates in the request. If it was just restricted once converted, that would solve the problem.

"restrict any additional comments/work on the original issue. Many times, the original assignee on the issue isn't the one managing the project nor are they the one working a task within the project."

[#7]

I agree. At the very least, please add "Resolved By" to the list of fields that can be tracked in the Update Feeds.

Nothing related to Resolvables is available under Setup > Interface > Update Feeds as a field that can be added.

[#8]

That would be brilliant! At least we wouldn't have to navigate to Project Details to have a look at that.

[#9]

A problem for us is when people go back to an old email notification and click on it thinking they are opening the project, but instead the email was from the request and they begin comment in there and the comments never go anywhere. Can the request be locked down once it's converted.

[#10]

I have submitted similar enhancements, for consideration as part of the overall solution:

https://one.workfront.com/s/idea/0874X000000sYnVQAU/detail

https://one.workfront.com/s/idea/0870z000000XiAqAAK/detail

[#11]

Is it possible to have any updates added to a request after that request has been converted also transfer over to the resolving project? No one monitors the requests for communication after conversion, so any questions/comments left there are almost certain to be left unanswered.