Issue Summary

When adding a comment during a workflow transition in the new transition experience, the comment visibility is incorrectly determined as internal even though it should be visible to all users. In the old transition experience, the same transition correctly treats the comment as external. This impacts customers who copy comments from software to JSM spaces because the comment is being added with the wrong visibility.

Steps to Reproduce

1. Configure an automation rule to check the visibility of a comment when added. Use the smart value in Log Action: 

   {{comment.internal}}

1. Open a work item with a transition that includes a transition screen.

1. Use the new transition experience to transition the item.

1. Add a comment during the transition and complete it.

1. Check the configured automation rule or resulting comment visibility.

1. Observe that the comment is marked as internal even though it should be visible to all users.

1. Repeat the same transition using the old transition experience.

1. Observe that the comment is correctly treated as external.

Expected Results

Comments added during transition in the new transition experience are classified with the same visibility as in the old transition experience.

The Log action for the smart value should be false

Actual Results

The Log action for the smart value will be true. If this comment is copied to JSM space, it is added as an internal comment.

Workaround

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