Cloning alludes to replicating. To clone an issue intends to rapidly make a copy issue inside a similar task. Cloned issues can be treated as another issue and altered like different issues.
A cloned issue is a totally independent issue from the first issue. Any move or activity made at the first issue doesn't affect the clone issue and the other way around. The main association between the first and the clone is the connection that is made.
Following data is conveyed from the first issue to the clone issue.
- Chosen one
- Target variant
- Fix variant
- Issue joins
- Substance of custom fields
Following data isn't cloned −
- Time following
- Issue history
Following are the means to clone an issue.
Stage 1 − Open an issue in the View page by tapping the Issue ID.
Following segments of the View Issue Details page will be shown.
- View Issue Details
- Clients Monitoring this Issue
- Include Note
- Issue History
Stage 2 − After opening the View Issue Details page, click the Clone button as appeared in the accompanying screen capture.
It opens the report page and every single accessible detail are replicated in the separate fields as appeared in the accompanying screen capture.
Stage 3 − At the base of the page, the first issue id is composed for the field "Relationship with the parent issue". Select the relationship of unique and cloned issue as appeared in the accompanying screen capture.
Stage 4 − The segment, Copy broadened information from parent issue. has 2 checkboxes − Copy Issue notes and Copy connections. Check these in the event that you need to duplicate the equivalent. As a matter of course, these are unchecked.
Stage 5 − After determination, click the Submit Issue button.