A scenario was brought to me today about a concern with our user's turnaround time metrics. What I'm using today is =IF([Status Summary]@row = "Closed", NETWORKDAYS([Assigned Date]@row, [Status Date]@row) - 1, "TBD"). This works great if the requests can be worked on in a timely manner. However, the issue at hand is that a more complex scenario exists where further research is being done to try resolving a request that is going to wind up taking a larger timeframe (i.e., 1.5 months). When most requests are turned around in 0-1 days, the fear is that the user's metric is going to be skewed because of this.
I'm sure others have encountered something similar to this and maybe some of you have great solutions to counteract this concern. I'm struggling to come up with something that doesn't overcomplicate things or impact the common scenarios as this isn't a frequent situation.
I could have them delete their name from the Assigned To field until they are ready to reengage on the item, then add their name back in, which would trigger the automation to update the Assigned Date, basically cutting out a large block of time.
Assigned Date is basically the creation date. There's an automation that populates a new Assigned Date anytime the Assigned To user is changed.
Status Date updates based on an automation that anytime the status changes, then a the current date is populated. Basically, when something is marked Complete, then this date should be populated for the last time.
