Issue Summary

When cloning work items, there is a checkbox in the clone dialog that lets end users decide whether to include comments in the clone. Some customers feel this control should not be exposed at the individual user level and instead should be managed from the Global Administration panel. The concern is that users may misuse or overlook this option and accidentally clone comments that are not supposed to be copied (for example, sensitive or internal comments).

Steps to Reproduce

1. Open an existing work item that contains one or more comments.
2. Click the action to clone/duplicate the work item.
3. In the clone dialog, observe the checkbox that controls whether comments will be included in the cloned item.
4. Leave the checkbox selected and complete the clone.
5. Confirm that comments from the original work item are copied into the cloned work item.
6. Note that there is no global/admin setting to disable or centrally manage the ability to clone comments; control is only at the end-user level via this checkbox.

Expected Results

• Administrators can configure whether comments are allowed to be cloned (globally or per project) via a setting in the Global Administration panel.
• If cloning comments is disabled by an admin, end users do not see the “clone comments” option or cannot change it.
• If cloning comments is allowed, admins can at least define the default behavior (e.g., “do not clone comments by default”) or restrict which types of comments can be cloned, reducing the risk of unintentionally cloning sensitive or irrelevant information.

Actual Results

• The ability to clone comments is only controlled through a checkbox in the clone dialog visible to end users.
• Users may unintentionally or inappropriately clone comments that should remain only on the original work item (e.g., internal notes, sensitive details, or off-topic discussions).
• Administrators lack a central configuration point in Global Administration to enforce comment-cloning policies, which can create governance, privacy, or compliance concerns.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available