Clockworthy

Getting started

Clockworthy is not on the Atlassian Marketplace yet. These steps apply once it is listed.

1. In Jira, open Apps → Explore more apps, search for Clockworthy and install it. You need to be a Jira admin to install apps.
2. Open a project. In its navigation you'll find Recurring work. Click it.
3. Select New schedule, fill in how often, the time and the issue to create, then Preview the next runs and Create schedule.

Clockworthy works in company-managed, team-managed and service projects.

How often a schedule runs

• Day numbers that a month doesn't have run on its last day: day 31 runs on 30 April and on 28 or 29 February.
• Every few days, weeks or months and quarterly count from the start date. A quarterly schedule that starts in December runs in March, June, September and December.
• Time zone: any IANA time zone, such as Europe/London or America/New_York. The default is your own Jira time zone. On the day the clocks go forward, a time that doesn't exist runs an hour later on the clock (01:30 becomes 02:30); when they go back, a time that happens twice runs once, at the second one.
• Start and end: a schedule starts today unless you choose a later date, and can stop after an end date.

Runs are checked every five minutes, so an issue appears within about five minutes of its time. Preview the next runs shows each run with its offset from UTC, so you can see the clock changes: for example Fri 26 Mar 2027, 09:00 (UTC), then Mon 29 Mar 2027, 09:00 (UTC+1).

The issue each run creates

If the last issue is still open: choose Create the new one anyway or Skip this run. A skipped run is recorded in the history with the open issue's key.

Who the issues are created as

Whoever creates or last edits a schedule is its owner, and each run creates the issue as them, using Atlassian's user impersonation for Forge apps. The owner is the reporter, and the issue appears in their activity like one they created.

• To add a schedule you need permission to create issues in the project.
• Only the owner or a project admin can edit, pause, resume, run or delete a schedule. Editing makes you the owner.
• If the owner can no longer create the issue, for example because they left the project or the issue type was removed, the run fails, the schedule pauses and the page says why. Fix the cause, then edit or resume it.
• When an owner's Atlassian account is closed, their schedules pause. Someone else can edit a schedule to take it over.

The Recurring work page

Every schedule in the project, with its rule, next run in local time, last run, owner and status (Active, Paused or Ended). For each one:

If Jira or Forge is unavailable when a run is due, the missed run is made once when it's back, not once for each missed time.

Not in this version

• Closing or moving the previous issue automatically when a new one is created.
• Adding issues to the active sprint, and sub-task checklists.
• A single page for schedules across all projects.
• Cron expressions. Clockworthy uses plain-words rules on purpose.

Data and privacy

• Clockworthy stores Atlassian account IDs of schedule owners and assignees, never names or email addresses. Jira shows current names when the page is viewed.
• As Atlassian requires, Clockworthy reports the account IDs it stores to Atlassian every week. When Atlassian says an account has been closed, Clockworthy replaces it with "(deleted user)" and pauses that person's schedules.
• Clockworthy has no servers of its own and sends nothing outside Atlassian. It is built to qualify for Atlassian's Runs on Atlassian programme. Its logs record only error types, status codes and counts.
• We, the vendor, cannot see your schedules or issues.
• Permissions it asks for: app storage; read and write Jira work, including on behalf of the schedule's owner so scheduled runs can create issues as them; and Atlassian's personal data reporting.

See also our privacy policy.

Troubleshooting

Changelog