Create Jira issues automatically on a schedule: standups, weekly reports, monthly invoices, quarterly reviews, maintenance checks. Plain-language repeat rules, no cron, and times that respect each schedule's time zone.
| Rule | Examples |
|---|---|
| Daily, every N days | Every day at 09:00 · every 3 days |
| Weekly on chosen days, every N weeks | Mon–Fri standup · every 2 weeks on Thursday |
| Monthly on a day or the last day, every N months | 1st of every month · last day of the month · every quarter (3 months) · every year (12 months) |
Each schedule has its own time zone and keeps the same wall-clock time across daylight-saving changes. Optional start and end dates.
{date} {day} {weekday} {week} {month} {quarter} {year} {n}, for example "Weekly report – week {week}". Tokens also work in the description.Jira settings → Apps → RecurPulse for Jira: allow only Jira administrators to manage schedules, limit RecurPulse to some projects, and see recent activity across all schedules. By default anyone who can create issues in a project can schedule issues for it, and people only see schedules for projects they can create issues in.
No. RecurPulse doesn't use Automation rules, so it doesn't count against your Automation run limits.
Jira runs RecurPulse every 5 minutes, so issues are created within 5 minutes of the scheduled time.
If the assignee, reporter, priority or due date can't be set (for example the person isn't assignable), the issue is still created without that field and the run history says why.
Schedules and run history are stored in Forge storage on Atlassian's infrastructure. Nothing is sent outside Atlassian. See the privacy policy.
Email support@puzaricloud.in with your Jira site address. We reply within one business day (Monday–Friday, India time).