<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=15981) </details> <!--IssueSummary end--> ### Description I think recurring issues would be an awesome addition to gitlab. I could see it being use for multiple things (QA issue/tracking, If you have a set monthly release date, automatic issues for test cases.) ### Proposal On the issues page, have a checkbox. When checked, it makes a date picker available. The system then creates a background job?, to create the new issue. ### Links / references No links and/or references at this point. How does your organization plan/tackle regular occurrences like that? Maybe I am just tired, and need some sleep. The solution could already be in gitlab, and I just haven't discovered it. As always. Thanks, and peace!