That information is stored in special tables which you really can't report on.
If you want to be able to report on it, you can use metrics. Metrics are rows in a table, which you can report on. They capture things that happen to a record that would otherwise be overwritten or only saved in the sys_audit table.
Navigate to: Metrics > Definitions and create a "field value duration" metric for the assignment group field on the sc_task table. From that point onwards, each time a catalog task is assigned or reassigned to a different group, a row (metric instance) containing the group, task number and start and end date-time will be saved.
Below is an example for that same metric, but for the incident table. Notice the rows below the definition (stored in the metric_instance table). We can see that INC0010032 was assigned from the database group to the hardware group at 13:41:31 on the 18th of march.
You can join the sc_task table the metric_instance table in a database view. This will create a table where each sc_task is joined to all of its metric instances. In fact you might already have such a database view in your instance, with a table name of "sc_task_metric".
That information is stored in special tables which you really can't report on.
If you want to be able to report on it, you can use metrics. Metrics are rows in a table, which you can report on. They capture things that happen to a record that would otherwise be overwritten or only saved in the sys_audit table.
Navigate to: Metrics > Definitions and create a "field value duration" metric for the assignment group field on the sc_task table. From that point onwards, each time a catalog task is assigned or reassigned to a different group, a row (metric instance) containing the group, task number and start and end date-time will be saved.
Below is an example for that same metric, but for the incident table. Notice the rows below the definition (stored in the metric_instance table). We can see that INC0010032 was assigned from the database group to the hardware group at 13:41:31 on the 18th of march.
You can join the sc_task table the metric_instance table in a database view. This will create a table where each sc_task is joined to all of its metric instances. In fact you might already have such a database view in your instance, with a table name of "sc_task_metric".
There is usually a database view already included, which you can get to by typing sc_task_metric.list in the application navigator search bar.
If it does not exists, navigate to System Definition > Database Views and create one like this:
More information can be found here:
Hope this helps, if so I would be grateful if you marked this as correct.
