Documentation — Weekly Timesheets for Jira

Weekly Timesheets for Jira gives you a Monday–Friday grid for logging time across all your Jira projects, with a submit-and-approve workflow and CSV export for payroll or billing. Hours you enter are saved as ordinary Jira worklogs, so they stay in Jira and work with everything else you already use.

Quick start

1. Install the app from the Atlassian Marketplace into your Jira Cloud site (requires app install permission).
2. Open Jira → Apps → Weekly Timesheets.
3. Use the + Add issue box to search by issue key or summary and add issues as rows.
4. Click any Mon–Fri cell and type your time (e.g. 1.5, 1h 30m, or 0:30). It saves automatically as a Jira worklog.
5. When the week is done, click Submit for approval. The grid locks and your approver is notified in their Approvals tab.

The weekly grid

Rows are issues, columns are Monday through Friday, and each cell holds the time you logged that day. The grid shows daily totals (per column), row totals (per issue), and a grand total. Use the arrows or This week to navigate between weeks.

Entering time

Click a cell and type a duration. Accepted formats: a decimal number of hours (1.5), hours and minutes (1h 30m, 2h, 90m), or h:mm (0:30). Cells save on blur or Enter — there’s no save button. While a cell is saving it’s briefly locked so you can’t double-submit. Clearing a cell deletes that day’s worklog.

Adding and removing rows

The + Add issue search matches partial issue keys and summary text. A week holds up to 30 issue rows. Removing a row takes it off the week but keeps the logged time in Jira — removing a row never deletes worklogs (clear the cells if you want to remove time).

Copy last week

Copy last week carries last week’s issue rows into the current week with zero hours, so you can start from your usual set of issues instead of re-adding them.

Submit & approve workflow

A week moves through four states:

• Draft — editable. The default state.
• Submitted — you clicked Submit. Editing is locked and the week appears in your approver’s queue.
• Approved — your approver accepted it. Locked.
• Rejected — your approver sent it back with a comment. The week reopens for editing; fix it and resubmit.

A status banner at the top of the grid always shows where the week stands.

For approvers

If anyone is assigned to you as their approver, an Approvals tab appears. It lists submitted weeks from the people you approve. Open one to see their grid read-only, then Approve or Reject with a comment. You can export a single reviewed week, or use Export approved (CSV) to download every approved week across your team in one file.

Approver mapping (admin)

A Jira administrator opens Jira Settings → Apps → Weekly Timesheets settings and maps each person to a single approver. One approver per person. A person cannot approve their own timesheet. Only Jira administrators can view or change these mappings — the app enforces this on the server, not just by hiding the screen.

CSV export

Exports are in a long format suitable for payroll/billing: one row per logged entry, with columns issue, user, date, hours, comment, project. The file is generated in your browser and downloaded directly; it does not pass through any Midgaard server. Issue keys are written so spreadsheet apps don’t mis-interpret them.

How your data is handled

Hours are saved as standard Jira worklogs attributed to you. Week structure, status, and approver mappings live in Atlassian’s Forge Storage; nothing leaves your Atlassian instance. Every action runs with your own Jira permissions. See the Privacy Policy for full details.

FAQ

The Approvals tab isn’t showing. It only appears if someone is mapped to you as their approver. Ask your admin to set the mapping, then reload.

I can’t edit my week. It’s probably submitted or approved (editing is locked). A rejected week reopens for editing.

Removing a row didn’t delete my time. That’s by design — removing a row only hides the issue from the week. Clear the cells to remove worklogs.

“You don’t have permission to log work on …” You need the Work on issues permission on that issue in Jira. Ask your Jira admin.

Why only 30 rows? It keeps a week fast to load and is more than a typical weekly timesheet needs.

Roadmap (post-v1)

Deliberately not in v1, but on the radar based on demand:

• Billable vs. non-billable flags
• Invoicing, rates, and budgets
• Holiday / PTO / absence tracking
• Multi-step or project-scoped approval chains
• Locking of past periods

Tell us what you need at the support address below and we’ll prioritize.

Support

Bugs, questions, and feature requests:
GitHub Issues · Discussions · piotr@midgaard.software

We aim to respond within two business days. Please include your Atlassian site URL and a screenshot when reporting bugs.