Just been testing the fix in 7604 listed above.
From what I can see the headline issue of details being lost when the EDIT REQUEST button is used is resolved.
However that sort of uncovers a flaw as far as I can see it - that of in appropriate settings being left on requests.
The page only has options for 'LEAVE AS IS' and then specific named items for SITE, GROUP & TECHNICIAN

So with a request that is configured as
SITE: OFFICE A
GROUP: SUPPORT
TECH: JOHN

You go to EDIT REQUEST and select
SITE: OFFICE A
GROUP: DEVELOPMENT
TECH: Leave as is

Save it

The request ends up as
SITE: OFFICE A
GROUP: -
TECH: JOHN


What I was trying to achieve was to send a request /batch of requests that were being worked on by a specific technician to a different team so they could look at it. John is NOT in Development.

What I would have expected to occur was
SITE: OFFICE A
GROUP: DEVELOPMENT
TECH: Unassigned

Either the EDIT Request screen needs to have the option - NOT ASSIGNED added to it, or the logic of the re-assignment process needs to check that what is being asked makes sense and when it doesn't then make it make sense, what is being asked for should override what is on the request.

Am I misunderstanding the function of the screen or is this a bug that can be resolved quickly please.

Regards,
Andy