You can use this feature if you have to close the current release faster then previously scheduled and package it for deployment without deleting any of the work already completed. The deferred change request will not be discarded, but will be available for the future use.

As a Revision Manager, you can defer change requests if business reasons require you to move changes to a future revision.​ You can also use this option to promote limited changes quickly without losing your work.

Note: You cannot use the action to defer change request for standard change requests (CR).

1. Log in to Pega 1:1 Operations Manager as the Revision Manager.
2. Go to Revision Management, and then click the name of Current revision.
3. In the Change requests within this revision table, click the More iconDefer next to the change request that you want to defer.
4. Confirm the deferring by clicking Yes button in the Defer change request window.
5. Complete the Reason field, and then click Defer.Result: As a result, the deferring removes the change request from the existing revision and the Team Lead can reassign the change request to a new revision. The removed change request goes to Deferred status, and you can see it on the Team Lead's change request landing page. Note: For more information about re-association of the change request, see Adding change request back to the revision.

For example: A change request (OpsCR-4) has been resolved to create U+Bank Gold Account action, but the change is not ready for the current release and business wants you to move this change to the future revision. In this case, Revision Manager can use the Defer option to dissociate the changes from the current release.