---
title: "Records in Issue View, Jira Software boards and Jira Service Desk Queues"
canonical: "https://www.techtime-initiative.com/space/EasyTime/4882594/Records+in+Issue+View%2C+Jira+Software+boards+and+Jira+Service+Desk+Queues"
format: markdown
---
### What is it?

EasyTime records time when different [tracked events](https://techtime-website.atlassian.net/wiki/spaces/EasyTime/pages/4883003) occur. This includes commenting on an issue, resolving an issue and viewing an issue.

Work logs created will have distinct [messages that can be configured](https://techtime-website.atlassian.net/wiki/spaces/EasyTime/pages/5046769) to your liking – to produce timesheets that require [minimal review](https://techtime-website.atlassian.net/wiki/spaces/EasyTime/pages/5046349) and manual editing and can be sent to customers as part of your billing process.

When viewing an issue, after 17.5 seconds initial delay, EasyTime will record time when in the main 'Issue View' screen, in the 'Issue Navigator' opened in 'Detail View' mode, in the 'Issue View' opened from a queue within Jira Service Desk and in the 'Detail View' on the Jira Software board.

In all modes that allow switching to another issue without reloading the whole screen, e.g. Jira Service Desk queues, subject to the initial delay and [conflict resolution](https://techtime-website.atlassian.net/wiki/spaces/EasyTime/pages/4882953) with the already created work logs, EasyTime should be able to follow the user when they switch from issue to issue and produce timesheets that accurately reflect the reality of what the user was doing.

### How to configure?

This behaviour is [configurable](https://techtime-website.atlassian.net/wiki/spaces/EasyTime/pages/4882562); and [tracking can be paused](https://techtime-website.atlassian.net/wiki/spaces/EasyTime/pages/4882516), and the individual work logs created while "clicking around" can be removed with [undo functionality](https://techtime-website.atlassian.net/wiki/spaces/EasyTime/pages/4882434).

> ℹ️ Unlike comment and resolve events, the view event is very "opportunistic". When the user just views an issue, what does it mean? Were they reading it intently, or were they discussing it with their colleagues? Despite our desire to send the automatic work logs directly to billing, we found that it is better to make the message on the view event sound *deliberately robotic, *unlikely to be mistaken for one typed in by a human. These work logs can be [easily spotted during review](https://techtime-website.atlassian.net/wiki/spaces/EasyTime/pages/4948091) and changed if required.