Need: The Ticket Version Number is a valuable identifier available in the Ticket Summary view but is currently not available in either the Live or Historical Power BI datasets.
Why It Matters: In many operational use cases, especially when analyzing change over time or reconciling updates to tickets, the version number helps differentiate whether a ticket has been revised and how frequently updates are occurring. This is especially important for auditing, compliance, and internal tracking purposes.
Value Add:
Enables more accurate trend analysis around ticket modifications and potential ability to leverage existing rules and tools to address more efficiently.
Supports change monitoring and escalation tracking.
Facilitates improved operational reporting.
Aligns reporting capabilities with the UI experience for consistency.
Adding this field would bridge the gap between UI data and reporting insights and provide more granular visibility across reporting audiences.
Need:
The Ticket Version Number is a valuable identifier available in the Ticket Summary view but is currently not available in either the Live or Historical Power BI datasets.
Why It Matters:
In many operational use cases, especially when analyzing change over time or reconciling updates to tickets, the version number helps differentiate whether a ticket has been revised and how frequently updates are occurring. This is especially important for auditing, compliance, and internal tracking purposes.
Value Add:
Enables more accurate trend analysis around ticket modifications and potential ability to leverage existing rules and tools to address more efficiently.
Supports change monitoring and escalation tracking.
Facilitates improved operational reporting.
Aligns reporting capabilities with the UI experience for consistency.
Adding this field would bridge the gap between UI data and reporting insights and provide more granular visibility across reporting audiences.
5 Votes
0 Comments
Login or Sign up to post a comment