NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

Hi everyone,

Thank you for your feedback. The JIRA product management team is working to make jira.atlassian.com a more valuable service by ensuring it accurately reflects the relative prioritization of feature requests. Remember that jira.atlassian.com is one of the many sources of feedback we use when planning the JIRA roadmap. For more details, please read our post on the subject.

With that said, we have chosen to close this issue. While we recognize that it would be valuable in a number of use cases, we have not been able to prioritize this issue for the past 10 years and do not expect this to change in the foreseeable future.

There are a number of ways to achieve recurring issues in JIRA:

• TheScheduler, available for JIRA Server.
• Recurring Tasks, available for JIRA Cloud.
• Simply clone issues issues prior to closing them. You can also automate this with the Create Issue on Transition add-on.
• Use any kind of scripting tool, like a Cron job, and create issues via the JIRA REST API.
• There are a number of discussions of different strategies on Atlassian Answers here, here, here, and here.

I recognize that this may come as disappointing news. Please remember that our goal is to make jira.atlassian.com more useful to you by ensuring that the every open suggestion is something we truly plan to implement.

As always, please do not hesitate to contact me with questions.

Regards,
Dave Meyer
Product Manager, JIRA Platform