When someone logs work on a Jira issue, NexerIQ can turn that worklog into a line on the right employee's work journal — so the time is captured for approval and billing without anyone re-entering it. Add, change, or delete a worklog in Jira and the matching journal line follows. This guide shows how to switch it on, how Jira users are matched to employees, and how mapping rules set the right project, phase, task, and dimension. (Connect Jira first — see Connecting NexerIQ to Jira.)

Before you start

• Jira is connected to NexerIQ and the customer field is set up.
• The Work Journal feature is enabled, so there are work journals for time to land in.

Step 1 — Turn on worklog sync

On the Jira Integration settings page, find Work log time entries and tick Create work-journal lines from Jira worklogs. Two things appear:

• A Default work project picker — choose the project that should receive time logged on issues that have no customer (internal work).
• A webhook URL (after you Save) for the next step.

Click Save.

Step 2 — Tell Jira to send worklogs

Copy the webhook URL shown on the page. In Jira, go to System → Webhooks, create a webhook, paste the URL, and enable it for the worklog created, worklog updated, and worklog deleted events. From then on, Jira notifies NexerIQ whenever someone logs, edits, or removes time.

Step 3 — Match Jira users to employees

NexerIQ needs to know which employee each Jira user is. It works this out automatically by email the first time a user's time comes through, so in most cases there's nothing to do. To match everyone up front, click Match Jira users to employees: NexerIQ reports how many it linked and lists any it couldn't — either because no employee has that email, or because more than one does — so you can fix them.

Step 4 — Set up mapping rules (optional)

Beyond hours and description, NexerIQ can fill in the work project, phase, task, and a billing dimension automatically, using mapping rules in the Work log mapping section.

Each rule matches on any combination of the issue's project (space) key, component, label, and team — leave a field blank (or *) to ignore it — and then sets the work project, phase, task, and/or dimension. Every condition you fill in must match.

When several rules match the same worklog, the most specific one (the one with the most conditions) wins for each field, with priority breaking ties; less specific rules fill in anything still empty. A rule with no conditions is a catch-all fallback.

Use New rule to add one, and Validate rules to check that every rule points at a real project, phase, task, and dimension. NexerIQ only shows the phase, task, and dimension options your company uses — if a feature is off, its fields are hidden.

What lands in the work journal

• Each worklog becomes a line on that user's employee work journal — the hours, a description built from the issue and the worklog comment, the billable flag, and anything your rules set.
• The work project is chosen in this order: a comment override, then a project set by a matching rule, then the issue's customer project (created automatically if needed), then the default work project for issues with no customer.
• Billable hours are worked out by your time rounding rules when the journal is processed — for every worklog, billable or not — see Work project time rounding. Non-billable time can still appear on the invoice as a complimentary (free) line.
• If the worklog is later edited or deleted in Jira, NexerIQ updates or removes the matching line.

Power-user shortcut: overrides in the comment

You can steer a single worklog from its comment by adding a tag in square brackets. For example, [c: ACME01, ph: PS101, ot] books the time to customer ACME01, phase PS101, and marks it as overtime. Supported keys include c (customer), p (project), phase, task, dim (dimension), and ot (overtime). A comment override always wins over the mapping rules, and the tag is removed from the description saved to the journal.

Tip

Matching is by email, so if a Jira user's email isn't on their NexerIQ employee record, add it to the employee's emails — then run Match Jira users to employees again and the link will succeed.