Why when I convert a request/issue with a proof, the proof doesn't convert?

[MegSVT]

We have several users who like to submit requests with a proof that includes the markup edits. This is such a timesaver for both our submitters and designers. Why is it though that when I convert the request to a project, the proof doesn't follow along with it? 

Yes, there are workarounds, (uncheck the box to tie to original resolution) or (once the project is created, go back to the original request and move the proof to the project) but those are timely and frustrating. 

Am I missing something or we really cannot convert a request with a proof & comments to the project?

[Madalyn_Destafney · Accepted solution]

Wow, I didn't even know this behavior, but after some research, apparently that is how it goes even as far back as this Idea from 2022. You should upvote it bc that is definitely not ideal.

More documentation on this here, I guess only possible if you don't tie the resolution to the issue?

[MegSVT]

How do I do that?

[Madalyn_Destafney]

If you're referring to voting on the Idea, just click the Idea linked in my post and Like it (or Vote, I forget the term). Just like Liking a post.
If you're referring to not tying the issue resolution to the project, that's in Setup but if you're used to tying them I recommend keeping that or definitely looking into pros/cons of tying/not tying for your org.