![]() Ticket Data: Any ticket data fields you’ve created can also be mapped into the ticket reporting dataset.Resolution Time: The time (in minutes) between when the ticket was created and when its status was changed to “Closed.” This is mapped as a Text Value, but can also be mapped as a Numeric Value.Root Cause: Root causes can be set in a workflow and then selected by a ticket owner.At this time, the only source available is “Survey.” This is saved as a Text Value. They will be pulled in as a Text Set or Text Value field depending on the question type or Embedded Data they are mapped from. #PAMFAX PRICING ISO#Qtip: For date fields to pull into ticket reporting pages, they need to be mapped in ISO format (YYYY-MM-DD). Ticket Notes: Any ticket notes fields that you’ve added on your ticket workflow in the Follow-Up Details section can be mapped into the ticket reporting dataset.ĭata analysis programs for understanding ticket pricing iso#.They will be pulled in as a Text Set or Text Value field depending on the question type the note is built on.īelow are a few example widgets to help understand how the feature can be used: A simple bar chart widget that shows the priorities of tickets that are closed, in progress, and open.(Simple chart widget with Metric: Count, X-Axis Dimension: Status, Data Series: Priority, Display Options: Show Data Values, Stack Chart.) A simple line chart widget of Average Resolution Time grouped by month. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |