In order for request deployment of refactoring changes to be performed, it is necessary to make sure the refactoring changes have been tracked by a request. When you perform actions that will result in refactoring, such as exporting a file to a project, or moving a project folder, those changes will be recorded against the request ID that you supplied when you performed that action. For refactoring operations to occur in areas associated with stages other than the initial stage, you must promote that request to the required stage and then the refactoring changes will be reflected in the areas associated with that stage when the request is deployed.
For projects, it is advisable to set the project option:
Request required to refactor
This means that a user is required to provide one or more request IDs when they perform an action that results in refactoring, such as exporting an item or renaming a project folder, otherwise the action will not be completed.
For streams, it is advisable to set the option:
Valid request must be specified when delivering changes
In the case of streams, refactoring changes take place in the work area and are then delivered to the stream. Using the request that was specified when the changes were delivered means that the request can be used to deploy any refactoring changes that occurred.