Jira Worklog Review
Use this skill to review Jira worklog for a target day, compute total logged time, and close the 8-hour gap with either existing issues or a create-new-issue workflow.
Trigger Phrases
- "Review my worklog"
- "Check my jira hours"
- "Did I log enough time today?"
- "Review worklog for [date]"
- "Suggest what to log if I am under 8h"
- "Create a new Jira task and log work"
Tools
This skill relies on Atlassian Jira MCP (Jira toolset):
mcp_mcp-atlassian_jira_searchmcp_mcp-atlassian_jira_get_worklogmcp_mcp-atlassian_jira_get_user_profile(optional)mcp_mcp-atlassian_jira_add_worklogjira_search_fieldsjira_get_field_options- Jira create issue tool in the same MCP set (for creating issues in
TL)
Preconditions
- User can access Jira and has permission to read issues/worklogs.
- User can create issues in project
TLand log work. - Field
(BU) Projectexists as custom fieldcustomfield_10232.
Guardrails
- Default to read/analyze first; only create issue or add worklog after explicit confirmation from user input.
- Keep date explicit (
YYYY-MM-DD) and compute total bytimeSpentSeconds. - If under 8h, keep iterating suggestions/actions until total reaches or exceeds 8h, or user stops.
- If a required Jira tool call fails, show the exact failed step and ask for the minimum missing info/permission.
Workflow Router
- Resolve inputs:
date(default: today)user(default:currentUser(), resolve accountId when filtering worklog entries)
- Load
references/workflows/01-review-daily-worklog.md. - If total
< 8h, loadreferences/workflows/02-suggestions-under-8h.md. - If user chooses create-new flow, load
references/workflows/03-create-issue-and-log-work.md. - Repeat suggestion loop until total
>= 8hor user stops. - Render final response using
references/templates/worklog-review-response-template.md.
Minimal Response Contract
Always return:
Date: target review date.Total logged: hours and minutes.Gap to 8h: remaining duration (or0).Actions taken: issue keys logged/created and durations.Next options: continue suggestions loop or stop.
Failure Handling
(BU) Projectfield not found or mismatched metadata: stop create-new flow, show returned fields, and ask user/admin to confirm field mapping.- No available
(BU) Projectoptions: stop create flow and request Jira configuration check. - Create issue or add worklog failed: report exact tool step and error, then offer existing-issue logging as fallback.