Add an Xray "Duplicate Test Cases" feature that supports bulk duplication while preserving original summaries and all test content.

Description
When cloning Test issues in Jira, the standard clone operation automatically prefixes the Test summary with "CLONE -". While this behavior may be appropriate for unique work items such as Stories, Tasks, or Defects, it creates unnecessary overhead for Test Management workflows where test cases are frequently duplicated and reused. As a result, users must manually edit each cloned Test to remove the prefix, especially when duplicating large sets of test cases.

A dedicated "Duplicate Test Cases" capability in Xray would streamline test reuse by allowing users to duplicate one or multiple Tests while preserving the original summary and all relevant Test information.

User Friction

• Every cloned Test requires manual editing to remove the "CLONE -" prefix.
• Bulk duplication of Tests creates significant cleanup effort.
• Test names become inconsistent until manually corrected.
• Additional Jira automation rules are often required solely to remove the unwanted prefix.
• The current cloning experience is not optimized for common test management workflows where copying Tests is a frequent activity.

_{Steps to Reproduce (Right Now) / Actual Result}

1. Open an existing Xray Test issue.
2. Use Jira's Clone action.
3. Create the cloned Test.
4. Observe that Jira automatically prefixes the summary with "CLONE -".
5. Repeat for multiple Tests.

Actual Result:

• Each cloned Test is created with a modified summary containing the "CLONE -" prefix.
• Users must manually edit every Test to restore the desired title.
• Test duplication becomes time-consuming when performed at scale.

^IMPACT

• Increased administrative effort for QA teams.
• Reduced efficiency when creating regression suites or reusable test libraries.
• Inconsistent naming conventions across repositories.
• Additional dependence on Jira automation to compensate for standard cloning behavior.
• Productivity loss becomes substantial when duplicating dozens or hundreds of Tests.

^{What Would Improve If Solved}

A dedicated Duplicate Test Cases feature would allow users to:

• Select one or multiple Tests.
• Duplicate them into a chosen Test Repository folder.
• Preserve the original summary without adding "CLONE -".
• Retain Test steps, expected results, datasets, labels, attachments, and other relevant metadata.
• Maintain traceability to the source Test through history or metadata rather than modifying the summary.
• Eliminate the need for automation rules and manual cleanup.

Impact on Stakeholders: Reduces manual effort for QA teams, simplifies test repository management, minimizes reliance on automation workarounds, and improves efficiency and consistency across organizations.

_{Current Workaround}

• Use Jira Clone to duplicate Tests.
• Manually edit each cloned Test and remove the "CLONE -" prefix.
• Alternatively, create Jira automation rules to automatically update cloned summaries after creation.

_{CONTEXT & EXAMPLES}

In many organizations, Tests are reused across:

• Multiple releases.
• Different products sharing common functionality.
• Regression testing cycles.
• Regional or customer-specific testing variations.

Duplicating Tests is therefore a routine activity rather than an exception. A workflow optimized for Test reuse should preserve meaningful Test names while maintaining traceability to the original source.

Concrete Example

• Original Test: Verify user can reset password using email verification.
• Current Result: CLONE - Verify user can reset password using email verification
• Desired Result: Verify user can reset password using email verification

Workaround Risk: Reliance on manual edits or automation adds maintenance overhead, introduces potential errors, and remains inefficient for large-scale test duplication.

Suggested Enhancement: Add an Xray "Duplicate Test Cases" feature that supports bulk duplication while preserving original summaries and all test content.