New

Require a Jira issue on chosen tasks

A task can now require every new time entry on it to name a Jira issue that exists, set where the task is set up — like required notes, per task.

On a project's edit page, tick Needs Jira beside a task, and new time on that task has to name a Jira issue — Engineering on one client can need one while Engineering on another does not.

The issue is checked against Jira when the entry is saved. An issue Jira does not have is refused; so is saving while Jira is not answering, with a message to try again, rather than letting an unchecked issue through. The rule holds everywhere time is logged: the timesheet, the timer (which asks when you start it), the assistant, Slack and the API.

Entries made before the rule are left alone: you can still fix their hours or notes. Only new entries, entries moved onto the task, and changes to an entry's issue are checked.

← 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