Features
What is it?
When a tracked event that is eligible for merging occurs on the same issue after a delay, and no other work logs on other issues have been created in that gap, EasyTime can ask the user if a separate work log should be created or if the original one should be extended to cover the gap.
Consider the case when the user views the issue, triggering the View Issue event, then goes away to work on resolving the issue and comes back to the issue sometime later. In the quest to produce timesheets that accurately reflect the reality of what the user was doing, EasyTime will ask if the merge should be performed.
If the start of the second work log is within the limit of silent merge – the work logs will be merged without a prompt. If the second work log starts outside the configurable time limit, a separate work log will be created automatically without prompting.
The intent is to ensure all time working on a task is recorded, even when you're not working in Jira, but also ensure that breaks and time on other tasks are logged correctly.
Prompting to merge currently only applies to view events. Any other events outside the silent merge limit will create a separate work log.
How to configure it?
Navigate to the EasyTime Configuration Screen.
The Parameter "Prompt to Merge Limit" controls how close should sequential work logs on the same issue be to still be considered for merge with an explicit prompt to the user. The default value is 2 hours. Choose 1-minute, 6-minute, 15-minute, 30-minute, 1-hour, 2-hour, 4-hour and 8-hour intervals and press Save at the bottom of the screen.
More information
Find EasyTime on Atlassian Marketplace, install via UPM, do the minimal configuration as per our Getting Started with EasyTime guide, review our Glossary, our FAQ and the full list of EasyTime Features. Enjoy consistent and accurate timesheets in real-time.
If you have any configuration questions or ideas for improvements, you can always contact us.
Contact us