Please consider the following specific scenario:
* The requester sends a request in SDP.
* 1st level support is provided by a group in SDP.
* 2nd level support is provided by a group outside SDP.
* 2nd level communicates the resolution to 1st level support.
* 1st level support communicates the resolution to the requester.
* The report needs to show all closed requests with an indication of:
                - The creation date of the request.
                - The date when the request was transferred from 1st level to 2nd level.
                - The request closure date.
                - The group who solved the issue (this can be 2nd level outside SDP).

Since we have no possibility to create a report based on the request history it’s difficult to keep track of the date when the request was transferred from 1st level to 2nd level. Which option would you consider?
1° Using closure codes (this is not a preferred option because it’s a system wide setting and this does not track the date).
2° Using resolution templates (indicating if the resolution was provided by 1st level or 2nd level but this does not track the date).
3° Using levels (for 1st level and for 2nd level but this does not track the date).
4° Defining custom fields (ex. 2nd level incident created incident on / 2nd level support group name).
5° Duplicating the request and linking both requests (with the reference request assigned to 1st level and the linked request assigned to a virtual 2nd level).
6° Creating a problem from the request.

We should reduce the number of manual actions but also make sure we have all data we need for the reports. The solution should be generic and re-usable. What is the best practice?