Recurring Issues for Jira

Daily standups, weekly reports, monthly reviews. The issues appear on time, where your team works.

• Plain schedules: every day, every weekday, chosen weekdays, every N weeks, or monthly (including the last day). No cron.
• Correct time zones: each rule keeps its local time across daylight saving changes.
• Sprint-aware: new issues go straight into the active sprint, on Scrum and team-managed boards.
• Tidy: optionally close the previous unfinished copy when a new one is created.
• Templates: {{date}}, {{weekday}}, {{week}}, {{month}}, {{year}} in titles and descriptions.
• Safe: one catch-up issue after downtime, never a flood. Runs on Atlassian, so no data leaves Atlassian.

Getting started

1. Install the app from the Atlassian Marketplace.
2. In Jira, open Apps → Recurring issues and click New recurring issue.
3. Pick the project, issue type and schedule. The preview shows the next five runs. Save.
4. Use Run now to create one immediately and check the result.

FAQ

Who is the reporter? The user who created the rule. If Jira doesn't allow setting the reporter, the issue is created without it instead of failing.

The issue wasn't added to the sprint. The project needs a started sprint on a Scrum or team-managed board. The rule shows a warning when no active sprint is found.

What happens if my subscription ends? Your rules are kept but no new issues are created until the license is active again.

Questions? Contact support.