To enhance ticket timing insights and support more accurate reporting around compliance behavior, it would be highly beneficial to include the Original Due Date in the historical Power BI dataset. his field is already available in Export reporting but is currently missing from the Power BI data model.
Currently, only the final or adjusted due date is available, which limits the ability to:
Identify when tickets were renegotiated after the original due date
Track trends in due date extensions or delays
Understand operational friction or constraints related to initial timeframes
Accurately report on response timeliness against original expectations
Having access to the Original Due Date alongside the current Due Date would allow teams to:
Build cleaner SLA performance tracking
Analyze root causes for due date adjustments
Report with greater transparency to leadership and stakeholders
Improve resource planning and ticket lifecycle forecasting
This is especially impactful in industries or regions where due date renegotiation is common, as it would give compliance and operations teams a clearer picture of where and why targets are shifting.
1 Votes
1 Comments
L
Lindsay Rennerposted
9 days ago
Admin
Our Development and Data teams are currently evaluating this request as part of ongoing improvements to the Power BI reporting experience. While we don’t have a confirmed timeline yet, we’ll be sure to provide updates here as soon as more information becomes available.
Please keep the feedback coming—it’s incredibly helpful as we prioritize future enhancements.
To enhance ticket timing insights and support more accurate reporting around compliance behavior, it would be highly beneficial to include the Original Due Date in the historical Power BI dataset. his field is already available in Export reporting but is currently missing from the Power BI data model.
Currently, only the final or adjusted due date is available, which limits the ability to:
Identify when tickets were renegotiated after the original due date
Track trends in due date extensions or delays
Understand operational friction or constraints related to initial timeframes
Accurately report on response timeliness against original expectations
Having access to the Original Due Date alongside the current Due Date would allow teams to:
Build cleaner SLA performance tracking
Analyze root causes for due date adjustments
Report with greater transparency to leadership and stakeholders
Improve resource planning and ticket lifecycle forecasting
This is especially impactful in industries or regions where due date renegotiation is common, as it would give compliance and operations teams a clearer picture of where and why targets are shifting.
1 Votes
1 Comments
Lindsay Renner posted 9 days ago Admin
Our Development and Data teams are currently evaluating this request as part of ongoing improvements to the Power BI reporting experience. While we don’t have a confirmed timeline yet, we’ll be sure to provide updates here as soon as more information becomes available.
Please keep the feedback coming—it’s incredibly helpful as we prioritize future enhancements.
0 Votes
Login or Sign up to post a comment