Edits made to request to flow to converted projects

[#1]

Description - It would be nice if any edits made to the request after it is converted to a project, flows down to that converted project as well for ease of data consistency and accuracy. 

Why is this feature important to you - This saves the admin team time otherwise spent on copying data from request to project.

How would you like the feature to work - if we are able to do this, the teams working on the project will not miss any important edits made to the request that never flowed to the project.

Current Behaviour - Request edits do not flw to converted project, hecne there is a mis match of data between the two objects.

[#2]

When you convert an issue/request to a project, there is the ability to give Contribute rights to the requestor. Then rather thn them updating the original request, they can update the actual project directly.

This can be set as the default behavior

[#3]

While I see your point @GrahamJarrett, in some environments like ours, we don't want requestors "seeing" the project, not even Contribute. There is a sort of wall/fence between the Requestor and the nuts-n-bolts of the project to avoid unnecessary micro-management, too many input vector, scope creep, etc.

So letting the requestor update the Request side and have it migrate to the Project side (or provide a Project notification that the Request side has been modified) would be ideal.

We went back and forth about even saving the request. WF is kinda binary: delete the request once converted to a project (which is a foolproof way to keep scope creep/drift from happening) or keep the request but expose the project to the requestor. We mitigated this through a series of reports with no links to the project for the curious, but as others point out, this leaves the request open to edits that the planners may fail to notice.

Not a win either way, more like "pick your poison."