The Jira Get Worklog action retrieves the worklogs entered for a specific Jira issue (task, story, bug, etc.). This makes it easy to track who spent how much time on a task.
Technical Specifications
Retrieve Work Logs: Returns all worklog records for the specified issue_key. The returned data type is JiraWorklogsResult (One).
Parameters:
settings (Object – required): Contains Jira connection settings. The Jira API setting defined via Config Manager must be selected.
issue_key (String – required): The key of the issue for which worklog information is to be retrieved must be entered (e.g., PROJ-101).
Data Source Compatibility:
A fixed value (Fixed Value) can be entered (e.g., TASK-12).
Can be connected from dynamic sources (Current, Action Result, Method Input).
Jira Get Worklog Application Steps
1. Adding an Action in UI Design
Go to the screen where you want to display the worklog information.
E.g. Add a “View Working Hours” button.
Click on the button → + ADD ACTION → Jira→ Jira Get Worklog.
2. Define Parameters
settings: Select your Jira connection from Configuration Manager.
issue_key: Enter the key of the issue for which you want to retrieve worklog information (e.g., SUP-234).
3. Using the Returned Data
The returned result is of type JiraWorklogsResult. It contains:
author: The user who entered the worklog,
timeSpent / timeSpentSeconds: Time spent,
started: Date/time the work started,
updated: Time updated, etc.
This data can be linked to a table, list, or detail card.
Usage Scenario: Worklog Tracking for a Task
A project manager wants to see the time spent on task SUP-234.
Steps:
Click the “View Worklog” button.
The Jira Get Worklog action is triggered.
The returned result is displayed on the screen in a table format:
User: mary.watson
Time Spent: 3h
Start: 2025-09-16 09:00
Update: 2025-09-16 12:15
Jira Get Worklog Advanced Customizations
Filtering: The returned worklog list can be filtered by date or user.
Reporting: Worklogs can be converted to total time and presented as a graph or summary report.
Combination: With the Jira Get Issues → Jira Get Worklog chain, project tasks are listed first, then the working times for each task are retrieved.
Technical Risks and Controls
The issue_key must be entered correctly. If entered incorrectly, no results will be returned from Jira.
There may be permission restrictions. The user may not have permission to view all worklog information.
Large data risk: If there are too many worklogs, a limit/offset may be required for performance.