Worklog360 Docs

Time Tracking & Timesheets with AI

Use Worklog360 MCP with ChatGPT, Claude, or Codex to log time, manage Jira worklogs, track timers, and submit timesheets using everyday language. This guide is for individual contributors and anyone responsible for their own time tracking.

Quick start: Ask “Log 2 hours on PROJ-16 for today.” For more ideas, jump to advanced prompts.

Worklog360 MCP guides: Overview · Time Tracking · Team Approvals · Automation Examples · Tool Reference

Before you begin: Connect Worklog360 MCP to your AI assistant. For prompts that need to find Jira issues or read actual logged hours across a period, also connect Atlassian MCP. You can find the setup guides in Worklog360 MCP — Overview.

1. Log Time on Jira Issues

Tell your assistant which Jira issue you worked on, when, and how much time to record. Include a description or billable duration if relevant.

What you want to do

What to ask your AI assistant

Log time today

“Log 5 hours on PROJ-16 today.”

Log time for another date

“Log 3 hours on PROJ-16 for yesterday, working on the API integration.”

Specify billable time

“Log 5 hours on PROJ-16 for Tuesday, with 3 hours billable.”

Log time across issues

“For today, log 3 hours on PROJ-12 and 5 hours on PROJ-16.”

Log several days

“Log 8 hours on PROJ-16 on Monday and Tuesday, and 6 hours on PROJ-20 on Wednesday.”

Find the issue first

“Find the Jira issue assigned to me about invoice synchronization, then log 2 hours on it for today.”

How it works: Worklog360 MCP creates the Jira worklog under your authenticated user and applies Worklog360 billable-time handling. Finding issues by description requires Jira context, typically from Atlassian MCP. The assistant should resolve any ambiguous issue or date before creating entries.

2. Edit Existing Worklogs

You can update an existing worklog without opening Jira. Ask the assistant to locate the entry first if you are unsure which one you want to change.

What you want to do

Example prompt

Find a worklog

“Find my worklogs on PROJ-16 from yesterday.”

Change logged duration

“Change yesterday’s 5-hour worklog on PROJ-16 to 6 hours.”

Change billable duration

“Make only 3 hours of my 5-hour entry on PROJ-16 billable.”

Update description

“Update my worklog description on PROJ-16 to ‘Fixed invoice synchronization errors.’”

If several worklogs match, the assistant should show the candidates and ask which one to edit. Only worklogs you are authorized to change can be updated.

3. Track Time with Timers

Use a timer while working on an issue, then create a worklog when you are ready.

Action

Example prompt

Start a timer

“Start tracking time on PROJ-16.”

Check timer status

“What am I currently tracking time on?”

Pause the timer

“Stop my current timer.”

Log a paused timer

“Log the time from my last stopped timer to its Jira issue.”

Note: Stopping a timer does not automatically create a Jira worklog. Logging a paused timer is a separate action, and the assistant should verify that the entry was created.

4. Review Your Timesheet

Worklog360 supplies your timesheet requirements, planned hours, approval status, and assigned approvers. To show actual logged or billable hours, the assistant also retrieves the corresponding Jira worklogs.

What you want to know

Example prompt

Review this week

“Show my timesheet for this week.”

Find missing time

“Compare my logged hours with my required hours this week and tell me which days need attention.”

Review a previous period

“Show my logged hours by day for last week.”

Check approval status

“Has my timesheet for last week been submitted or approved?”

Find approvers

“Who is assigned to approve my timesheet?”

5. Copy Last Week’s Worklogs to This Week

This is an example of a multi-step AI workflow: instead of manually re-entering recurring time, ask the assistant to prepare worklogs based on a previous period.

Show my worklogs from last week. Prepare the same issues, hours, and billable durations for the corresponding weekdays this week. Check whether I have already logged time on those days, show me the proposed entries, and ask me to confirm before creating them.

The assistant should:

  1. Retrieve last week’s actual Jira worklogs.

  2. Map each entry to the corresponding day in the current week.

  3. Check existing entries this week to avoid duplicates and flag any holiday or day-off conflicts where that information is available.

  4. Show you the proposed Jira issues, dates, hours, and billable hours.

  5. After confirmation, create the new worklogs and report any unsuccessful entries.

This workflow requires access to historical Jira worklogs, typically through Atlassian MCP, plus Worklog360 MCP for creating entries. Copied entries should reflect work actually performed; the assistant cannot determine that solely from last week’s records.

6. Complete and Submit a Timesheet

Review the period, correct any missing or inaccurate entries, and submit the complete timesheet for approval.

Action

Example prompt

Prepare for submission

“Check my timesheet for last week, compare logged and required hours, and show me what needs fixing.”

Fill gaps using your instructions

“I worked 8 hours on PROJ-16 on Thursday. Add that entry and check if anything else is missing.”

Submit a week

“Submit my timesheet for last week.”

Submit a month

“Submit my timesheet for October.”

Worklog360 MCP supports weekly and monthly timesheet submissions. Submission status and permitted actions depend on your organization’s timesheet configuration and permissions.

7. Advanced Prompts: Combine Several Actions

These prompts demonstrate how an AI assistant can coordinate multiple tools in a single conversation.

Workflow

Natural-language prompt

Complete today’s work

“Find my assigned Jira issues and help me split today’s 8 hours across the tasks I worked on.”

Correct several entries

“Find my entries on PROJ-16 this week, show them to me, and help me correct their billable hours.”

Compare weeks

“Compare my logged hours this week with last week, grouped by Jira issue.”

Review then submit

“Review my timesheet for last week, show missing hours, help me correct them, and submit it after I confirm.”

8. Frequently Asked Questions

Do I need both MCP connections?

Worklog360 MCP handles Worklog360 time tracking and timesheet actions. Atlassian MCP is recommended for finding Jira issues and reading historical worklogs, especially for multi-step prompts such as comparing weeks or copying entries.

Can the assistant log time for other people?

The current standard logging workflow creates worklogs under the authenticated Jira user. Logging for other people is not part of this guide.

Can I use natural language rather than exact tool names?

Yes. Ask for an outcome in ordinary language. Your AI assistant selects and combines the connected tools as supported by its platform and your permissions.

Can it automatically copy my worklogs every Monday?

A scheduled assistant can prepare recurring entries if its platform supports scheduled tasks and connected MCP tools. Review proposed worklogs before they are created; scheduling is not a feature of the MCP tools themselves.

The examples illustrate supported tools and composed workflows. Exact results depend on available Jira data, Worklog360 permissions, and your AI assistant’s ability to coordinate connected tools.