• Feedback Policy:
      We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.


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

      Atlassian Update - 20 February 2015

      Hi everyone,

      Thank you for your feedback. The JIRA product management team is working to make a more valuable service by ensuring it accurately reflects the relative prioritization of feature requests. Remember that 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:

      I recognize that this may come as disappointing news. Please remember that our goal is to make 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.

      Dave Meyer
      Product Manager, JIRA Platform

      Original request

      If JIRA is used as a task tracker, it would be useful if one could schedule the periodic creation of an issue (aka task), for instance, "Reboot server" every Monday. The 'issue created' email would act as the notification to the user when the issue was (automatically) created. Alternatively, a single issue could cycle through a workflow, with an email notification on the initial state.


          Issue Links



              Unassigned Unassigned
              jefft Jeff Turner
              194 Vote for this issue
              120 Start watching this issue