Assigning a CI to an RITM, changes the assigned_to field on that CI to the user making the assignmentDescriptionAssigning a CI to an RITM, changes the assigned_to field on that CI to the user making the assignmentCauseThis is caused due to the OOB business rule Business rules - Assign from Stock: CI field on RITM will be used to assign that CI to the user(requested_for). Whenever a user is requesting for any CI, then that will be added to this field of RITM. Now when this happens the below BR runs. Business rules - Assign from Stock:- When configuration_item on request item(sc_req_item) table changes, then CI from cmdb_ci and child tables is updated with install_status as pending install, assigned_to to requested for from RITM. A configuration item is assigned from stock to requester in the user. This is due to the Business Rule Assign from Stock on the Requested Item table. This sets the Install Status for the CI to Pending Installation (The system assumes some work is being done on this CI to support the request), the Assigned to of the CI to the Requested for on the Request, and the Assigned date and time to the current date and time. ResolutionThis is an expected behavior. The configuration item column will only display the records which are in "In stock" status which once saved will get the assigned to and status updated to pending install. So the next request will not have the CI selected by me listed in the list because the reference qualifies will restrict the record since the status is no more "In stock " and is changed to "Pending install."