log time spent on ticket dynamic time tracking
ART-2021_KNOWLEDGE_NODE-26
Install the\n   [Ticket age in engineering](/marketplace/ticket-age-in-engineering)\n   from the DevRev marketplace.\n2. Add all of the **stage names** that reflect that engineering work is planned\n   or is being done for that ticket. The stages you specify are the ones that\n   track time spent on engineering. The default values are the default DevRev\n   engineering stages for tickets.\n3. Select whether time spent on engineering should be displayed in hours or\n   days.\n4. Click **Install
Ticket age in engineering | Automate | Snap-ins | DevRev
ART-2028_KNOWLEDGE_NODE-24
[Snap-ins](/docs/snapins)\n[Automate](/docs/automate)\n[Work duration](/docs/automations/work-duration)\n\nWork duration\n=============\n\n[Work duration](/marketplace/work-duration) offers the ability\nto track how much work issues and tickets took to complete, measured by time\nspent in work sessions.\n\nThe snap-in adds a new attribute to tickets and issues which automatically\ncalculates the work duration for that item. Work duration is meassured in time\nspent through work sessions. A work
Work duration | Automate | Snap-ins | DevRev
ART-2021_KNOWLEDGE_NODE-25
spent on engineering for that ticket. There can be multiple engineering\nsessions. An engineering session starts when a ticket moves from a\nnon-engineering stage to an engineering stage and it ends when it moves from an\nengineering stage to a non-engineering stage. You should select which ticket\nstages reflect engineering work and if the time spent should be shown in hours\nor days.\n\nInstalling the Ticket age in engineering snap-in\n------------------------------------------------\n\n1.
Ticket age in engineering | Automate | Snap-ins | DevRev
ART-15688_KNOWLEDGE_NODE-29
system automatically validates:\n\n   * Date format and range (within last 10 days to next 10 days)\n   * Hours and minutes values\n   * Prevents logging when both hours and minutes are zero\n3. **Confirmation**: After successful validation, the effort is logged and a confirmation message appears in the timeline.\n\nSupported object types\n----------------------\n\nThe Effort logger snap-in works with the following object types:\n\n* **Tickets**: Log effort against support tickets, bug reports,
Effort logger | Automate | Snap-ins | DevRev
ART-15688_KNOWLEDGE_NODE-28
effort logs as custom objects with structured data\n\nHow to use\n----------\n\n1. **Access the command**: In the timeline of any ticket or conversation, type the following command:\n\n```\n```\n1 /log_effort\n```\n```\n\n1. **Enter effort details**: The snap-in prompts you to enter:\n\n   * **Date**: The date when the effort was performed (MM/DD/YYYY format)\n   * **Hours**: Number of hours worked (0 or positive number)\n   * **Minutes**: Number of minutes worked (0-59)\n2. **Validation**: The
Effort logger | Automate | Snap-ins | DevRev
ART-2021_KNOWLEDGE_NODE-24
[Documentation](/docs)\n3. [Snap-ins](/docs/snapins)\n[Automate](/docs/automate)\n[Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\n\nTicket age in engineering\n=========================\n\n[Ticket age in engineering](/marketplace/ticket-age-in-engineering)\noffers the ability to track how much time tickets spend on engineering, measured\nby ticket time spent on engineering stages.\n\nThe snap-in adds a new attribute to tickets which automatically calculates the\ntime
Ticket age in engineering | Automate | Snap-ins | DevRev
ART-15688_KNOWLEDGE_NODE-24
[Supported object types](#supported-object-types)\n\n1. [Documentation](/docs)\n3. [Snap-ins](/docs/snapins)\n[Automate](/docs/automate)\n[Effort logger](/docs/automations/effort-logger)\n\nEffort logger\n=============\n\nThe effort logger snap-in allows users to log effort against objects with comprehensive validation and custom schema management. It provides a seamless way for teams to track time spent on tickets, conversations, and other objects within
Effort logger | Automate | Snap-ins | DevRev
ART-15688_KNOWLEDGE_NODE-26
set, the default is 365 days.\n\n![]()\n\nConfigure the appropriate roles and permissions to access and modify the custom effort log objects based on your organization's requirements.\n\nFeatures\n--------\n\n* **Effort logging**: Log hours and minutes worked against objects\n* **Date validation**: Automatic date format validation with MM/DD/YYYY support\n* **Custom schema management**: Automatic creation and validation of custom schema fragments\n* **Timeline integration**: Create timeline
Effort logger | Automate | Snap-ins | DevRev
ART-15688_KNOWLEDGE_NODE-25
DevRev.\n\nInstallation\n------------\n\n1. In DevRev, go to **Settings** > **Snap-ins** and click **Explore Marketplace** in the top-right corner.\n2. In the DevRev marketplace, find **Effort Logger** and click **Install**.\n\nConfiguration\n-------------\n\nIn **Settings** > **Menu**, the following configuration option is available:\n\n* **Date Threshold (days)**: The date threshold for the effort log (in days). If the date is older than the threshold, the effort log is not created. If not
Effort logger | Automate | Snap-ins | DevRev
ART-2695_KNOWLEDGE_NODE-30
*start*, *pause*, and *stop*. This configuration is available through the **OLA metrics for issues** snap-in. **Issue Resolution Time** is the default metric. For additional metrics, contact our support team.\n\n1. Go to **Settings** > **Integrations** > **Snap-ins**.\n2. Locate and view the **OLA metrics for issues** snap-in.\n3. Click on **Configure** within the snap-in.\n4. Select stage values for the **Issue Resolution Timer** to start, pause, and stop. Resuming a paused timer requires no
Operational-level agreement | Computer for Support Teams | DevRev
ART-2695_KNOWLEDGE_NODE-31
additional configuration; it automatically resumes when the issue stage updates to any stage not designated for stopping the timer.\n5. Click **Save**.\n\nAssigning stage values for starting and stopping the timer is mandatory. Ensure that each stage value is unique across the start, pause, and stop options. Any configuration changes will only apply to issues created after the changes are made.\n\n![]()\n\nUninstalling the snap-in will remove the OLA metric from all active and new issues, which
Operational-level agreement | Computer for Support Teams | DevRev
ART-2028_KNOWLEDGE_NODE-25
session starts when a work item is created\nor reopened and ends when the item is closed. The work duration can be shown in\nhours or days.\n\nInstalling the Work duration snap-in\n------------------------------------\n\n1. Install the [Work duration](/marketplace/work-duration) from\n   the DevRev marketplace.\n2. Select whether work duration time should be displayed in hours or days.\n3. Click **Install snap-in**.\n\n[PreviousUser group
Work duration | Automate | Snap-ins | DevRev
ART-1483_KNOWLEDGE_NODE-24
[here](https://github.com/devrev/snap-in-examples/tree/main/6-timer-ticket-creator)\n\nWas this page helpful?YesNo\n\n[Using a snap-in to perform an external actionUp Next](/public/snapin-development/tutorials/perform-external-action)\n\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\n\n[Enterprise grade security to protect customer dataLearn more about it.](https://devrev.ai/blog/soc-compliance)\n\nProduct\n\n  *
Using a snap-in to perform a DevRev action — DevRev | Docs
ART-15515_KNOWLEDGE_NODE-41
start a timer, use the following method:\n\n```\n|  |  |\n| --- | --- |\n| 1 | DevRev.startTimer(_:properties:) |\n```\n\nTo stop a timer, use the following method:\n\n```\n|  |  |\n| --- | --- |\n| 1 | DevRev.endTimer(_:properties:) |\n```\n\nFor example:\n\n```\n|  |  |\n| --- | --- |\n| 1 | DevRev.startTimer("response-time", properties: ["id": "task-1337"]) |\n| 2 |  |\n| 3 | // Perform the task that you want to measure. |\n| 4 |  |\n| 5 | DevRev.endTimer("response-time", properties: ["id":
Features | DevRev | Docs