This chapter provides information about the recreate issue feature.
The Recreate issue feature allows you to copy issues to the same or another project with its fields and structure without creating a template. The feature is enabled by default and you don’t need to configure it, however, you can disable it in Global Configuration - Visibility Settings.
If you recreate an issue A-1 from project A to project B, you can select which children of A-1 and linked issues from project A will be also recreated in project B. Remaining issues that may be linked from other projects will be recreated in these projects.
Try the live demo below
Fields like Reporter, Comments, and Statuses won’t be copied.
If you recreate an existing task, Issue Templates for Jira Cloud automatically copies the first comment regardless of the scope. In a parent-child structure only the first comment from each issue is copied.
Click the Three dots menu in the issue window.
Click Recreate issue.
Select a project you want to recreate the issue in. If you select your Template Repository project you can create a new template.
Select which child issues you want to recreate. To recreate only an issue select no checkboxes.
Select if you want to copy or recreate issue links.
Click Recreate.
The issue has been recreated with all selected elements.
Recreate child issues is a time-saving feature that gives you more control over the recreated structure. With this feature you can select which child issues you want to copy. You can copy tasks with sub-tasks, epics with stories, and initiatives with children.
There are three options to choose:
Recreate issue can also copy issue links.
You can select either of the three options:
To select which user groups can use Recreate issue follow instructions in the Global configuration chapter.
Issues recreated from any of your projects into the Templates Repository automatically become a templates (using the default template settings). You can customize its settings right after this action. An issue recreated from an existing template into the Templates Repository copies template’s settings.
Both ways allow you to create a copy of your issues as templates in the Templates Repository.