Get Started with EasyTime

We assume you have already installed EasyTime via UPM or have arrived to the configuration screen via the side panel link in the Admin interface, admin "." shortcut of the Configure button in UPM and have configured time tracking to enable users to record time (Cloud and Data Centre/Server).

Enable EasyTime by adding Tracked Groups

We recommend starting simple and using a small group of users when first trying the add-on. To add a user group to the list, just start typing as you would do in a regular group picker and available groups will show up. For example, to only track time for your Service Desk agents, add the corresponding group. The cloud default is jira-servicemanagement-users-<your instance name>. You can add as many groups as you like to this field later.

Select Tracked Projects

Now that you've selected users who will be enjoying our automatic real-time tracking, we need to tell EasyTime which Jira projects it needs to ignore. 

For example, if you enabled tracking for the Service Desk team, you may want to track time only on JSD projects that deal with external customers and require accurate billing. 

This can be achieved by filtering out all other projects using JQL in the "Ignore Configuration" field. To log time in TEST and the 'External Service Desk' projects only, insert the following JQL into the "Ignore Configuration" field:

This means that all projects that are not TEST or 'External Service Desk' will be ignored by the EasyTime app.

Decide if you want the starting times to be aligned to the grid

Excellent, you've narrowed your tracking to certain groups and Jira Projects; now it's time to decide how often you want EasyTime to create log entries. 

We bill our customers in 15-minute minutes, but your organisation might have different granularity. 

This is set using the "Minimal Unit of Time" field.  

Please note that by default, EasyTime aligns work log start times to the grid, which means if a user comments on an issue at 3:17 PM, the work log will begin at 3:15 PM.

Unchecking "Align time records to the closest time slot" while setting the minimal unit of time to 15 minutes will cause the 15-minute-long work log created for the user's comment left on the issue at 3:17 PM to start at 3:17 PM instead.

Example initial configuration:

Choose how you would like work logs to be merged

By default, if a user comments on an issue after first viewing it, the two work logs will be merged into a single work log, retaining the message corresponding to the comment event (being the higher priority event).

However, a separate work log will be created if the user views an issue after commenting on it. This behavior can be changed by selecting "Merge lower priority and keep old comment".

More information

Please review our Glossary, our FAQ  and our list of Features