Timesheet Management PRO is a Jira app for logging time and running a weekly submit → approve → (optionally forward) → lock timesheet workflow. It builds on everything Timesheet Management LITE offers - the advanced Calendar and Timesheet views, built on Jira’s own native worklogs - and adds approvals, team routing, locking, billing rates, and reporting on top.

Open Apps → Timesheet Management PRO from the Jira navigation. The first time you open it you may see the standard Atlassian consent screen. Every user grants it once, because the app acts as you when it reads and writes your worklogs. If the app can’t load your account straight after granting consent, reload the page.

If the site’s PRO license lapses or is cancelled, the app shows a license notice in place of every tab until the license is active again. Your worklogs stay in Jira either way.

To use the app’s time logging into Jira work items, a Jira admin sets Timesheet Management PRO as the site’s active Time Tracking Provider (Jira Settings → Work Items → Time tracking). Only one provider can be active at a time, so PRO and LITE can’t both be the provider on the same site.

Once that’s done, two things change on every work item:

• The Log work action opens the app’s worklog form, similar to Jira’s native Time Tracker modal, including the live time-remaining bar when the work item has an estimate.

• The work item’s Work log tab lists every worklog on it, with add / edit / delete controlled by your Jira permissions and by the timesheet workflow (a submitted or approved week is read-only).

App configuration lives in the app’s own Settings tab, open to Jira admins and to Timesheet Management admins (see Admin settings below).

• Date and time default to the current date and the nearest local hour.

• If the work item has a time estimate, the form shows a two-tone progress bar - time logged so far in one color, time remaining in the other, right below the time field. Time remaining is read-only and updates as you type; it isn’t re-fetched, so if someone else logs time on the same item around the same moment, refresh to see it.

• Worklogs can repeat every day, weekdays only, or on a custom schedule, and a repeat can later be changed for one occurrence, this and future occurrences, or all of them.

The Calendar shows your own worklogs one week at a time, on a day-by-day timeline. Each entry shows its work item and, if you added one, its description.

• Log time: click any empty part of the calendar. The time defaults to where you clicked, drag up or down first to set a duration.

• Edit an entry: click a worklog block to change its work item, date, time, duration, or description.

• Open a work item: click its key inside an entry to open it in Jira in a new tab.

• Move an entry: drag a block to a different time or day.

• Resize an entry: drag the top or bottom edge of a block.

• Delete an entry: open it and use the Delete button.

• Weekdays / Full week: defaults to weekdays only, and switches to the full week automatically if you have weekend entries. You can also toggle it by hand.

• Use the Week of date picker or the ‹ › arrows on the top right of the page to move between weeks.

• The Recent Work Items panel beside the calendar lists items you’ve recently logged against. Drag one onto the calendar to log time at that spot, or hide the panel with the × in its header (a Show Recent Work Items button in the toolbar brings it back).

Above the calendar, a row of four colored pills - Approved, Submitted, Draft, Rejected - totals how much of the week on screen is in each state, followed by a Total pill and a week status line (Not yet submitted with the due date when the site locks periods on a set day, Submitted, awaiting review, or Approved by a named approver). A Week locked badge replaces the status line when an admin has locked the week. The Submit Week button, a History link (see Week history) and, for an already-submitted week, a Recall link sit at the right of the same row (see Submitting a week for approval).

The Timesheet tab shows the same week as a grid, grouped by person and space - one row per person + space, with a running total. Click a row to expand it into a day-by-day breakdown of that space’s work items.

• Within an expanded row, click any day cell to see or edit the worklogs behind it.

• Click a work item’s key to open it in Jira.

• The Approver column shows who approves each work item’s timesheet - a named person, a “<group name> group”, or once approved, who approved it.

• Filters: Space, Status, and User. Nothing runs until you press Search - pressing it with nothing changed re-runs the week, which is how you pick up time a colleague logged since the grid was drawn. A small dot on the Search button means you have changed a filter that hasn’t been applied yet. Clear filters puts them back (Filters empty, User back to you).

• Saved views: save the current filters under a name, reapply, overwrite or delete them later, and share a view with colleagues by link.

• Export: the Export menu above the table downloads the current week as CSV or Excel.

• Same Weekdays / Full week toggle as the Calendar tab, and the same pills row: the four status pills, then Total, then the week status line (Not yet submitted, Submitted, awaiting review, or Approved by a named approver). When the site locks periods on a set day, the line also names the due date - the last day the week can still be submitted - and turns red once that day has passed.

• When the grid has no rows, the status pills, Total, History and Submit Week are hidden; only the status line stays.

From the Calendar or Timesheet tab, click Submit Week. A confirmation dialog shows the week and your total logged, and lets you add an optional note for your approver. Submitting is per space, per week - every space you logged against that week is submitted together.

If the week has any worklogs logged after their work item’s resolution date, submission pauses and a Resolve worklogs before submitting dialog lists them. Fix each one in place - use Replace Worklog to add a corrected entry on the right date and then delete the original, or just delete an entry that shouldn’t have been logged - then submit. (These same entries also show on the Corrections tab.)

A collapsible How timesheets get approved line on the Calendar and Timesheet tabs tells you where this week’s hours go once submitted. The route depends on the site’s approver mode:

• Space lead - each space’s lead approves worklogs on that space’s work items. If a space has no lead, its submissions go to no one and only admins can see them. An admin can then approve on the lead’s behalf, or set a space lead and ask the person to resubmit.

• Specific people or groups - a fixed set of approvers for the whole site; any one of them can approve.

• Per space - the approvers configured for each space, falling back to that space’s lead where none are set.

• Team Lead - worklogs go to the lead of the team named in the work item’s TMProTeam field. If that field is blank, they go to the lead of the person’s own team (or the parent team’s lead if their team has none). If the person is in several teams, the submission goes to the lead of each. If no team lead can be found at all, it falls back to the space lead.

While a week is submitted but not yet approved, a Recall link is available on the Calendar and Timesheet tabs. It opens a dialog to pick which space(s) to recall; those worklogs become editable again immediately, with no approver involved. Once a week is approved there is no recall - ask an approver to reject it, or an admin to unlock it if it’s locked.

An approver can send a submission back with a required reason. You’ll see a banner on the Calendar and Timesheet tabs the next time you open the app - “N of your submissions were rejected and are editable again” - listing each space, week, who rejected it, and why. The worklogs are editable again; fix them and resubmit. Use Dismiss to clear the banner.

Every change to a week’s approval state is recorded and kept: Submitted, Recalled, Approved, Unapproved, Rejected, Forwarded, Reopened by new time (time was logged into a submitted week), Needs re-approval (an approved worklog was deleted in Jira), Week locked and Week unlocked. Each entry shows when it happened, who did it (a person, Automatic for the scheduled lock, or Timesheet Management for the app itself) and a comment where there is one: the note typed at submit, the rejection reason, the forward note and who it went to, the worklog count and hours of an approval, or how many approved worklogs were deleted.

• The History link beside Submit Week on the Calendar and Timesheet tabs opens the timeline for your own week, across every space. It stays available after the week is submitted, approved or locked. On the Timesheet tab, an admin who has filtered to one other person sees that person’s week instead.

• Approvers open the same timeline for one row from the row’s action menu in the Approvals tab (History).

• Timesheet Management admins get a site-wide log under Reports → Approval history.

History starts from the day the feature was added to your site; earlier weeks show No history for this week yet.

The Approvals tab appears for anyone who can approve at least one space - a space lead, a team lead, a configured approver, someone a week was forwarded to, or a Timesheet Management admin (who can act on anything via View all). A badge on the tab counts weeks awaiting your approval plus any alerts (forwards to you, rejected weeks, approved worklogs since deleted in Jira). The badge updates after every approve, reject, unapprove or forward.

The tab has up to three sections:

• Pending Approval - every submitted week-and-space group waiting on you, one row each. Per row: Approve, Reject (reason required - it goes back to the submitter), Forward and History (the week’s timeline, see Week history). A row is blocked from approval while it contains a worklog logged after its work item’s resolution date; use Notify on that entry to message the person to fix it.

• Deleted After Approval - shows itself only when an approved worklog has since been deleted directly in Jira. The app records a durable snapshot at approval time, comments on the work item, alerts the approver, and reopens the group for re-approval.

• Approved - approved groups for the week selected in the top bar. Once the whole week is locked, an Export menu here downloads it as CSV or Excel (a copy taken before the lock could still change, so export waits for the lock).

In Team Lead mode, a freshly submitted week appears in your queue the next time you open or reload the tab.

The Actions menu on the Pending Approval header runs Approve all, Reject all, or Forward all across every row in the section that the per-row action would allow. Approve all asks for confirmation first.

Forward hands one row - one person’s week for one space - to one or more other people with an optional note. Each recipient gets their own copy and can approve, reject, or forward it independently. Forwarding is also how someone without approve rights passes a week to someone who has them. You can’t forward to yourself or to the person whose timesheet it is.

The Alternate approvers button lets any approver name a backup for a space they approve. The alternate gets the same approve rights alongside the original approver (it’s additive, not a hand-off), either permanently or until a date you set. Timesheet Management admins can manage alternates for anyone. This is self-service and separate from the admin-configured approver modes.

• Space, User, and Approved by filters narrow both sections. Press Search to apply them; a small dot on the button means a change hasn’t been applied yet.

• View all Timesheets (Timesheet Management admins only) widens the queue beyond the spaces you personally approve. Its hour totals come from a cache refreshed hourly; a banner appears if that cache has fallen behind. Approval status is always live.

• Weekdays / Full week toggles the day columns.

• Load older at the bottom of the Approved section reaches further back in time.

If you log time against a work item before it’s resolved and it’s resolved afterward, that entry becomes a violation after the fact - the resolution-date block only checks at the moment you log. Whenever you have entries like this, a Corrections tab appears (only when there’s something to fix), listing each one with the work item, the time logged, and when it was resolved.

For each entry, use Replace Worklog to add a corrected entry on the right date and then confirm deleting the original - or just delete it if it shouldn’t have been logged at all. You must clear these before you can submit the week.

Timesheet Management admins also see a View all violations toggle here for a site-wide, read-only list.

The Teams tab is open to Timesheet Management admins and to anyone who leads a team. It holds the app’s own teams - you name a team and put real Jira people on it; there’s no external directory involved.

• The tab opens on an org chart - one compact box per team, showing its name and who approves for it. Click a box to open that team’s detail view (Members and Overview).

• Create team adds a top-level team; give it a name, members, and an approver.

• In a team’s detail view, add or remove members and mark one or more as Team Lead. A team with no lead of its own rolls its approvals up to the team above it.

• A team can be given a parent team (drag on the chart, or use the parent picker) and can choose to follow its parent’s approver instead of naming one.

• Import replaces the whole roster, or one team’s members, from a CSV - use Download template for the format.

• A Team Lead who isn’t an admin sees only the teams they lead as editable; everything else is read-only.

Teams drive three things: the Team leads approver mode, the TMProTeam work item field, and the Reports → Teams roster.

TMProTeam is an ordinary single-select field on the work item, holding the name of one of the app’s teams. Nobody populates it automatically - someone picks a value like any other dropdown - and TMProTeam = "Team A" is plain JQL. In the Team leads approver mode it decides which team’s lead approves that item’s time; the Time in Status and Capitalization reports can also filter by it.

Which teams appear as options is set under Settings → Worklog Approvals → Approvers → Teams via each team’s linked spaces. A team with no linked spaces shows as an option everywhere.

The Reports tab is open to everyone. Each report has a Filter control and an explicit Search button - nothing runs until you press it, and a small dot on the button means you have changed something that hasn’t been applied yet - and most export to CSV or Excel. The period (Day / Week / Month / Custom, with prev/next) is set in the app’s top bar. Every report can save its filters as a named view, which you can reapply, overwrite, delete, or share with colleagues by link; in the Capitalization and Time in Status reports a saved view also remembers how the table was sorted.

• Time In Status - how long each work item has spent in each status, built entirely from work item history (it reads no worklogs). Configure which status columns show, group statuses into one column, and exclude weekends.

• Capitalization - a labor-capitalization schedule: one line per person × work item for the period, where a person’s time on an item is how long it sat in each status while they were assigned to it, bucketed CAPEX / OPEX / excluded by the policy an admin sets in Settings → Capitalization. Also history-based, so a past period always re-runs to the same figures. Large sites take a few weeks after install to fully populate.

• Teams - a read-only roster of every team and everyone on it, ordered by the team hierarchy.

• Billables (admin only) - what each person’s worklog hours in the period are worth, priced against the rows in Settings → Rates, grouped by vendor, person, and work item. People with no vendor or rate are shown in their own bucket (a toggle hides them).

• Approval history (admin only) - the site-wide log of every approval-workflow change (see Week history). The period in the top bar chooses timesheet weeks (Weekly / Monthly / Custom under the Range pill; the log is read in whole weeks, so there is no Daily): the log lists every action ever taken on those weeks, whichever day it happened, and a line above the table names the weeks it covers. Filter by Space, Person and Action, then press Search. Each row shows when the action happened, the timesheet week (start and end dates), the person, space, team, the action, who did it, and a Comment: the submit note, the rejection reason, the forward note and recipients, or an approval’s worklog count and hours. Exports to CSV or Excel. Very wide searches show only the newest events; narrow the weeks or pick people to see the rest.

The Columns menu on the Capitalization report adds work item fields to every row. On the left, pick a level; on the right, tick the fields to add (there is a search box). Fields already ticked move to the top of the list.

• This work item - each row shows its own value for the field.

• A hierarchy level, such as Epic - each row shows the value from the work item at that level above it (a Story row shows its Epic’s value). A row already at that level shows its own value; rows above that level stay blank.

Column changes apply when you press Search, the same as a filter change. Up to 50 added columns per report. Added columns are included in the export and in saved views.

The current and previous calendar months are always available in the Capitalization report. Shortly after a month ends, the app saves a frozen copy of that month’s report, and a saved month stays available for 12 months.

• The Past reports pill in the Capitalization report lists the saved months. Click one to open it. A saved month opens exactly as it was saved, with the same filters, added columns, and CSV or Excel export.

• Past reports open one whole month at a time.

• An export taken from a saved month carries a Snapshot saved line with the date the month was saved.

Timesheet Management admins can pull saved months into an ERP or finance system through a read-only REST API. It needs an OAuth 2.0 integration with the read:capitalization-report:custom scope, and the caller must be a Timesheet Management admin. See PRO - Capitalization REST API for setup, routes, and response formats.

The Settings tab is visible to Jira admins and to Timesheet Management admins. A few sections are Jira-admin-only, as noted below. Settings are grouped under three sub-tabs.

• Week starts on - the week boundary used by the Calendar and Timesheet tabs and by period locking.

• Weekends - which days are your weekend. The number you can pick follows Jira’s own working week. Used by every Weekdays / Full week toggle, the “Weekdays only” repeat preset, Time in Status’ Exclude weekends, and the Capitalization report.

• Timesheet Management admins (Jira admins only) - full super-user access: see every worklog, act on anything in Approvals, edit every setting outside the Jira-admin-only sections, and use the Capitalization REST API. Also copied on the daily digest emails.

• Error log (Jira admins only) - errors any user hits in the app, for troubleshooting.

• The policy the Capitalization report applies: pick a classification field (a work-item field or custom field), map each of its values to a treatment (capitalizable / expense / excluded), and choose which statuses count. Until a field is chosen the report has no policy and shows nothing.

• Counted statuses - Determines which status time will be calculated for the user. This can include old statuses (when a name of a status changes, historical status value does not change)

• Restriction - Limit the results based on the JQL. Capex/Opex results will not split with work items outside of the results. Changing the restriction rebuilds this month and last month in the background, and reports show as still building until it finishes. It can be changed up to 5 times per 24 hours.

  • Example: If user has 4 work items in Counted Statuses, but results only returns 2, values will split across 2 vs 4 work items.

Four pages:

• General - Prevent logging work after a work item’s resolution date, with a Don’t flag worklogs before date so turning it on doesn’t flood everyone’s Corrections tab with old history. Email digests (Jira admins only): one daily summary email on working days whenever there’s a resolution-date violation or a pending approval, sent by Jira from a placeholder work item you nominate.

• Periods - automatic period locking: Never (lock by hand only) or Lock when all approved and on the day of a chosen weekday. A fresh install starts on Lock when all approved and on the day of Wednesday; while a day is set, the Calendar and Timesheet tabs show each week’s due date. Don’t allow worklogs before the period containing a date is a hard cutoff, checked instantly with no per-period record (new installs set it to the install date). Below, a table of every unlocked period plus locked periods from the last three months, each with its own Lock / Unlock button and a note on why it hasn’t auto-locked. A locked period is frozen for everyone - no logging, editing, submitting, approving, or forwarding - and only an admin can unlock it.

• Rates - per-person billing rates for the Billables report: rate type, amount, currency, vendor, and date range, plus a default rate everyone without their own falls back to. Add rows by hand or import a CSV (which replaces the whole table).

• Approvers - choose the approver mode (space lead / specific people or groups / per space / team leads).

Every worklog you log through PRO is an ordinary, native Jira worklog - the same data you’d see if you logged it through Jira directly. PRO doesn’t keep a separate copy of your worklogs; Jira is the only place that data lives.

PRO does store its own workflow and configuration records: submissions, approvals (including a snapshot of the worklogs at approval time), the approval history log, forwards, alerts, per-person billing rates, a computed cache for the Capitalization report, monthly Capitalization Past reports (kept for 12 months), teams and their members, saved report views, records that link repeating worklogs together, a troubleshooting error log, and site settings. See the Privacy Policy for the full detail on what PRO itself stores, the Terms of Service for how the app is licensed and supported, and the Data Processing Addendum for subprocessor and international-transfer details.