- Get started
- About
- Glossary
- First steps
- Migration to Cloud
- Integrations points
- Create issue from template
- Recreate issue
- Apply template
- Apply template post function
- Legacy automation action
- Template custom field on issue create screen
- Apply template via issue property
- Configuration
- Repository
- Template's configuration
- Using templates
- Copy Epic
- Copy links and linked issues
- Copy Subtasks
- Copy Initiatives
- Default templates
- Using Variables
- Static variables
- Dynamic variables
- Smart defaults
- Basics
- Smart issues
- Smart users
- Smart dates
- Smart project
- How to use smart defaults
- Security
- Security statement
- App permissions
Recreate issue
This chapter provides information about recreate issue feature.
How it works?
The Recreate issue feature allows you to copy issues to the same or another project with its fields and structure. Feature works right after the app installation, and you don’t need to configure it.
If you recreate an issue A-1 from project A to project B, all 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.
However, fields like Reporter, Comments, and Statuses won’t be copied.
Steps
Watch the video below to better understand the usage of Recreate issue.
Issue recreated from any project into the Templates Repository
Issue recreated from any of your projects into the Templates Repository will become a template automatically (using the default template settings). You can customize its settings right after this action. What’s more, issue recreated from an existing template into the Templates Repository will use a copy of the template’s settings.
Both ways allow you to create a copy of your favorite issues as templates in the Templates Repository.
