Hi Vanessa,
Repeating this back so I'm sure I'm tracking - you have a requestor and they complete a request with it's attached Custom Form. In that form, there's a field called 'Custom Report Note'. They then have a dashboard that shows them all of their submitted requests and a column with the 'Custom Report Note' field that they can continually update weekly. At this point they can submit requests, access the dashboard and update that particular field as expected.
The PM (assuming?) then takes that Issue and converts it to a Project, which has an attached Custom Form at the project-level that mirrors the custom form attached to the request queue including that 'Custom Report Note' field. The requestor is able to see, but not update that version of the field if you reference the project-level version of it.
If everything I've summarized is accurate, then your troubleshooting is on the right track. A requestor license would not allow them to edit the project-level copy of the form/field no matter where you put it for them to view, they could only update the versions on the issue-level copy of the form. The best, albeit imperfect, analogy I've got is that it's a little bit like a survey you fill out online that emails you a copy of your answers afterwards. You could open the email copy of your answers (ie the issue-level) and make changes, but it wouldn't do anything to the data already stored with the company receiving the survey (ie the project level).
That doesn't mean you can't do what you're trying, it just has to be approached from a different angle. Your requestor will only ever be able to edit the field on the Issue itself, so your weekly status report has to be built at the same level. Instead of starting with a Project report, start with an Issue report instead and reference in whatever Project level data you need. Depending on what information you need in the overall report, a Work Item report might also help too.
Any of that helpful?
Katherine
