Associate multiple Changes to 1 Request Ticket

Hello,

Can you confirm if this is really the system behavior, i.e. you can only associate 1 Request Ticket to 1 Change Ticket?

If this is the case, then I suggest that in the next release this relationship be changed to 1 is to many. This will cover this scenario:
An RFC is raised to migrate server1 to server2, Change is implemented but needs to be back out fand closed as a failed implementation. A second attempt to perform the migration will have to be logged as a new RFC. In the current relationship, there is no way to associate the 2nd Change to the Request because the 1st Change is already associated to the Request. The 1st Change can not be re-used since we need to keep track of the # of failed Changes.

Please consider this in the enhancements to the Change Management module.

Thanks!