Fix

Tasks that need a Jira issue hold for copied rows and agent time

Copied rows and agent time no longer land on a task that needs a Jira issue, and the switch waits until Jira is connected.

A task that needs a Jira issue on every new entry now holds in three places it did not.

Copying rows. "Copy rows from last week", and copying a day's rows at zero hours, used to add an entry with no issue on such a task. Those rows are now left out, and the copy names the task so you can add that entry with its issue. Copying a day with time and notes was already checked.

Agent time. Agent time never carries a Jira issue, so it is no longer accepted onto a task that needs one, whether automatically or by you. It waits in your pending list with the reason: accept it onto another task, or discard it. An accepted agent entry cannot be moved onto such a task either.

The switch. Needs Jira on a project's tasks can be ticked only once someone in the workspace has connected Jira. Without a connection every entry on the task would be refused. A task already switched on keeps the rule, and the page warns you while Jira is disconnected.

← Everything that has changed

The hours, the invoices, and what they earned

Free for unlimited people. One paid plan, $10 per member per month, when you want HR, scheduling, timesheet approvals, scheduled backups, email from your own domain and scheduled reports.

Start free