Skip to:

Marketplace

Recurring Work for Jira

works with Jira Cloud

OVERALL RATINGS

INSTALLS

1

SUPPORT

  • Partner Supported

TRUST SIGNALS

Showing details for Cloud

Key highlights of the appCreate Jira issues on a schedule — daily, weekly, monthly, every N. No cron, no automation quota, and a run log you can see

hero

More details

Some work comes back every week: the Monday status report, the monthly access review, the quarterly maintenance ticket. This app creates those issues from a template you save once.

Daily, weekly or monthly, every N. Monthly takes a day of the month (clamped on short months) or the last day; quarterly is monthly, every 3. No cron string to write.

Every schedule carries its own timezone, so a 09:00 schedule still fires at 09:00 after a daylight-saving change.

Each schedule keeps its last 20 runs, each with the issue key it created — or, if it failed, the exact Jira error and a Retry button. Nothing turns itself off quietly.

Also: skip weekends, create N days early, relative due dates, an end date or run limit, and date tokens in the summary and description.

Runs on its own Forge schedule, so it uses none of your Jira automation quota. Built entirely on Forge — no external servers.

Good to know: the scan is hourly, so a 09:00 issue is normally created within the 09:00 hour.

Resources

  • App documentation

    Comprehensive set of documentation from the partner on how this app works

Privacy and Security

Privacy and security questionnaire has been filled by the partner

Privacy policy

Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.

Partner privacy policy

Security program

This app is not part of the Marketplace Bug Bounty program.

Integration permissions

Recurring Work for Jira integrates with your Atlassian app

Version information

Version 4.3.0for Jira Cloud

Release date
Aug 9th 2026
Summary
Hardened authorization: permission checks via Atlassian's authorize API
Details

Security hardening: the Run now action’s server-side permission check now also goes through Atlassian’s official Forge authorize API, alongside the existing project-permission verification. Same rule as before - Create Issues or project admin rights in the schedule’s project are required. No functional changes, no new permissions, no changes to existing schedules or data.

Payment model
Paid via Atlassian
License type
Commercial

Learn and explore

  • What’s Marketplace
  • App installation
  • About Atlassian
  • Atlassian resources
  • Search and ranking
  • Atlassian events
  • Atlassian foundation

Follow