What information is cloned when duplicating an issue in Jira?

When duplicating an issue in Jira, the information that gets cloned primarily includes the labels, issue type, and assignee. This ensures that the new issue retains critical identifiers and organizational attributes from the original one. Cloning is particularly useful for quickly creating related tasks or issues while maintaining context through these core attributes.

Labels help in categorizing the issue, the issue type defines the nature of the work (like bug, task, story, etc.), and the assignee automatically designates responsibility for the new issue. By including these elements, the cloned issue aligns more closely with the original, allowing teams to work on similar tasks more efficiently.

In contrast, other choices involve elements like comments and history, which are generally not duplicated to prevent clutter and maintain the integrity of the original issue's narrative. Similarly, while attachments and links contain helpful contextual information, they are not considered core attributes that are replicated in a clone. Priority and resolution settings are often tailored to the specific circumstances of the new issue, which is why they do not carry over through cloning. These distinctions are crucial for understanding how Jira manages issue duplication and helps keep projects organized and clear.