Hi Larry,
Using 'User Status' could be an option off course, but I believe to use "tasks' to track Rework/Repair delays along with user status.
For example, your present task is 0020 - TSRL/TSCO, and you decided to add rework task 0030 as TSOS, then this time should not be calculated in your report. But as soon as this is set, you can update another user status as 'ZQ1'. Now soon you have changed this 0030 task status form TSOS to TSRL, you can update another user status as 'ZQ2'. This means Rework actually started. Then when this task is completed to TSCO, you can update another user status like 'ZQ3'. With this setup, you can calculate the end-to-end delay time as difference between the task system status [TSCO - TSOS] and actual rework time as difference between [TSCO-TSRL].
Similarly you can track the status change form ZQ1 to ZQ3 and understand when the changes has happened.
Depends on the actual complexity of the requirement, the solution enhancement would vary to support it.
Thanks,
Arijit
Message was edited by: Arijit Banerjee