jira-worklog

You can bulk log work hours in Jira by generating and running a Bash script that uses JQL to discover tasks, validates assignments via changelog, and logs hours with duplicate detection. This automates repetitive monthly time-tracking entry.

Jira worklog automation prevents duplicate time entries by generating a script with built-in duplicate detection checks. It validates task assignments via the issue changelog and verifies prior logs before executing new worklog API calls.

Yes, automating Jira worklog entry via Bash requires the JIRA_API_TOKEN environment variable for token-based authentication. The generated script relies on this token to securely authenticate API requests when logging hours.

To run an automated Jira worklog script, you need MCP, jq, and python3 installed in your environment. You must also configure a .worklog.config.json file to provide the necessary settings for script generation and execution.

Yes, you can distribute work hours across recurring Jira tasks automatically by configuring the generated Bash script. It supports SP-weighted distribution to allocate effort proportionally across multiple discovered issues.

Yes, there is a dry-run safety feature for testing Jira worklog scripts before execution. This allows you to validate the generated commands, check task assignments, and verify hour distribution without modifying actual Jira time entries.