Yandex Cloud
  • Services
  • Solutions
  • Why Yandex Cloud
  • Pricing
  • Documentation
  • Contact us
Get started
Language / Region
© 2022 Yandex.Cloud LLC
Yandex Tracker
  • Getting started
    • Activating Yandex Tracker
    • Logging in to Yandex Tracker
    • Adding users
    • Configuring access to Yandex Tracker
    • Setting up Yandex Tracker
    • Working with Yandex Tracker
      • Home page
      • My issues
      • Working with issues
      • Favorite issues, boards, and dashboards
      • Personal settings
    • Migrating to Yandex Tracker
    • Disabling paid services
  • Yandex Tracker mobile app
  • Practical guidelines
    • Setting up Yandex Tracker for a development team
      • Overview
      • Creating a queue for a development team
      • Structuring issues
      • Using Agile methodologies
      • Configuring issue templates
      • Connecting repositories
      • Automating recurring actions
      • Integrating Yandex Tracker with other platforms
    • Setting up Yandex Tracker for a support team
      • Overview
      • Creating a queue for the support team
      • Accepting requests by mail and via forms
      • Configuring multi-tiered support
      • Sending emails from the issue page
      • Grouping requests by topic
      • Tracking the time it takes to process a request
      • Collect requests statistics
      • Configuring integration with third-party platforms
  • Concepts
    • Yandex Tracker overview
    • Concepts
  • Configuring queues
    • Overview
    • Creating a queue
    • Queue templates
    • Viewing issues in a queue
    • Changing basic queue settings
    • Configuring issue types and statuses
      • Overview
      • Configuring issue types
      • Create a workflow
      • Setting up statuses
      • Configuring transitions
      • Creating a resolution
    • Local issue fields
    • Adding a queue team
    • Setting access rights for queues
    • Advanced queue features
    • Viewing the history of queue changes
    • Deleting a queue
  • Working with issues
    • Creating an issue
      • Overview
      • Creating an issue via email
      • Creating an issue from a form
      • Cloning an issue
    • Editing an issue
      • Overview
      • Adding comments to issues
      • Creating a checklist
      • Editing issue links
      • Attaching images and files to an issue
      • Formatting text in issues
      • Executing macros
      • Voting for an issue
      • Moving an issue to another queue
      • Changing multiple issues
    • Setting up an issue reminder
    • Registering time spent
    • Adding issue fields
    • Viewing the history of issue changes
    • Getting access to an issue
    • Deleting an issue
  • Structuring issues
    • Overview
    • Links between issues
    • Projects
    • Components
    • Versions
  • Agile development tools
    • Overview
    • Creating a board
    • Working with an agile board
    • Editing and deleting a board
    • Sprints
    • Epics
    • Collaborative workload estimation
    • Burn down charts
  • Searching issues
    • Overview
    • Finding issues by key or name
    • Searching for my issues
    • Searching for issues in queues
    • Creating an issue filter
    • Query language
  • Notifications and subscriptions
    • Overview
    • Subscribing to notifications
    • Receiving update reports
    • Subscribing other users to queue updates
    • Notification settings
      • Overview
      • Notifications about your issues
      • Notifications about your subscriptions
  • Statistics and dashboards
    • Dashboards
      • Overview
      • Creating a dashboard
      • Widgets
      • Editing a dashboard
      • Shared access to dashboards
      • Making a dashboard your home page
    • Queue statistics
    • Gantt charts
  • Automation and templates
    • Overview
    • Triggers
      • Overview
      • Creating triggers
      • Setting trigger conditions
      • Configuring trigger actions
      • Editing and deleting triggers
      • Examples
    • Auto actions
      • Overview
      • Automatic issue updates
      • Scheduled issue creation
      • Editing or deleting auto actions
    • Macros
    • Templates
      • Overview
      • Creating a template
      • Editing a template
      • Deleting a template
      • Using shared templates
    • Variables
    • Using a form as a template for creating issues
  • Configuring an SLA for issues
    • Overview
    • Configuring rules
    • Work schedules
  • Integration with other services
    • Mail
    • Yandex Forms
    • Yandex Wiki
    • Messengers
      • Overview
      • Slack
      • Telegram
    • Setting up links to external applications
      • Overview
      • Setting up an external application
      • Sending your application data to the Tracker team
  • Developer tools
    • Plugin for IDE
    • API
    • Python client
    • Connecting repositories
  • Pricing policy
    • Pricing
    • Setting up a billing account
    • Topping up your personal account
    • Viewing service detalization
  • API reference
    • Overview
    • API access
    • Issues
      • Get issue parameters
      • Editing an issue
      • Creating an issue
      • Moving an issue to another queue
      • Find out the number of issues
      • Find issues
      • Release scroll view resources
      • Get priorities
      • Get issue links
      • Link issues
      • Get transitions
      • Make a status transition
      • Get the history of issue changes
    • Checklists
      • Create a checklist or add items to it
      • Get checklist parameters
      • Edit a checklist
      • Delete a checklist
    • Projects
      • Creating a project
      • Get project parameters
      • Get a list of all projects
      • Get a list of project queues
      • Edit a project
      • Deleting a project
    • Comments
      • Add comment
      • Get issue comments
      • Edit a comment
      • Delete a comment
    • Macros
      • Get queue macros
      • Get a macro
      • Creating a macro
      • Edit a macro
      • Delete a macro
    • External links
      • Get a list of external applications
      • Get a list of issue external links
      • Add an external link
      • Delete an external link
    • Attached files
      • Get a list of attached files
      • Download a file
      • Download a thumbnail
      • Attaching a file
      • Upload a temporary file
      • Delete a file
    • Queues
      • Creating a queue
      • Get queue parameters
      • Get a list of queues
      • Get queue versions
      • Get required fields for the queue
      • Deleting a queue
      • Restore a queue
      • Remove a tag from a queue
      • Automation
        • Receiving triggers
        • Creating triggers
    • Issue boards
      • Get parameters of all boards
      • Get board parameters
      • Creating a board
      • Edit a board
      • Delete a board
      • Columns
        • Get parameters of all columns
        • Get column parameters
        • Create a column
        • Edit a column
        • Delete a column
      • Sprints
        • Get all sprints of a board
        • Get a sprint
        • Create a sprint
    • Import
      • Import an issue
      • Import files
      • Import comments
      • Import links
    • Bulk operations
      • Perform a bulk move of issues to a different queue
      • Bulk changes to issues
      • Make bulk changes to issue statuses
    • Time tracking
      • Add a record of time spent
      • Edit a record of time spent
      • Delete a record of time spent
      • Get records of time spent
        • Get all records for an issue
        • Select records by parameters
    • Issue fields
      • Get global issue fields
      • Create an issue field
      • Get issue field parameters
      • Edit issue field names
      • Edit possible values of issue fields
      • Create an issue field category
      • Local fields
        • Create a local queue field
        • Get local queue fields
        • Get information about a local queue field
        • Edit a local queue field
    • Get information about the current user
    • Possible response codes
  • FAQ
  • Support
  1. Practical guidelines
  2. Setting up Yandex Tracker for a support team
  3. Tracking the time it takes to process a request

Tracking the time it takes to process a request

Written by
Yandex.Cloud

    When gauging the efficiency of your support team, the most common method is to track the time of their first response and the total time it takes to process a request. The lower these indicators are, the faster your team is at resolving users' issues.

    To manage the response handling time in Tracker, configure SLA rules for your queue's issues. An SLA rule lets you set the time limit for processing a request and enable a timer that starts and stops as certain events are triggered (for example, during issue creation, a status change, when adding an assignee, and so on).

    Let's set up SLA rules that will track the time of the support team's first response and the total request processing time.

    First response time

    To measure your support team's first response time, set up a timer that starts when an issue is created and stops when an employee sends a comment or email from the issue page.

    1. Go to SLA in the queue settings and click Create rule.

    2. Set the rule's name and choose Work schedule so that the timer is only active during business hours.

    3. Under Timeframes for issues, set the following parameters for all issues in the queue:

      • Set the time limit for the first response in the Time until expiration field. For example, if you want to set the time to 2 hours and 30 minutes, write 2h 30m.

      • In the Time until warning field, choose a time limit which triggers an automatic email reminder after expiring.

      Note

      If you want different issue groups to have different time limits, click Create new filter and set parameters for grouping these issues.

    4. Set the conditions that start and stop the timer:

      1. Under Start, add the condition Issue created.

      2. Under Stop, add the condition Received response from queue team.

    5. If you want to automatically email the employee responsible for the issue once the first response time has expired, select Notification → Overdue time limit and specify that employee's name or username in Email.

    6. Save your rule.

    Now the timer will be automatically enabled after the issue is created in the support team queue. It will count down until a support staff member from the queue team sends a comment or email from the issue page.

    Total request processing time

    If you want to measure the total request processing time, set up a timer that triggers during issue creation and stops once the issue status is updated to Resolved or Closed. You can pause the timer while the issue is in the Need info status so that the waiting time is not counted towards the total processing time.

    1. Go to SLA in the queue settings and click Create rule.

    2. Set the rule's name and choose Work schedule so that the timer is only active during business hours.

    3. Under Timeframes for issues, set the following parameters for all issues in the queue:

      • Set the time limit for resolving the issue in the Time until expiration field. For example, specify 8h if you want the limit to be 8 working hours.

      • In the Time until warning field, choose a time limit which triggers an automatic email reminder after expiring. For example, specify 6h if you want the limit to be 6 working hours.

      Note

      If you want different issue groups to have different time limits, click Create new filter and set parameters for grouping these issues.

    4. Set the conditions that start and stop the timer:

      1. Under Start, add the condition Issue created.

      2. Under Pause, add the condition Issue has the status → Needs info.

      3. Under Stop, add the condition Issue status changed to and select the Resolved and Closed statuses.

    5. Under Notification, set up notifications that trigger once the time limit is expired:

      • If you specified the warning time limit under Timeframes for issues, choose Email in the Warning field and specify the name or username of the employee responsible for the issue. This way, they will receive a notification once the set time limit expires.

      • If you want to automatically email the employee responsible for the issue once the resolution time limit has expired, under Overdue time limit, specify that employee's name or username in Email.

    6. Save your rule.

    Now the timer will be automatically enabled after the issue is created in the support team queue. The timer will be active until the issue status is updated to Resolved or Closed. If a support specialist asks the requester for additional information and updates the issue status to Need info, the timer will be paused and can only be unpaused after another status change.

    Was the article helpful?

    Language / Region
    © 2022 Yandex.Cloud LLC