Issue Summary

When a user utilizes Rovo (Chat or Agent) to change the issue type of a Jira work item (e.g., from Story to Bug), the "update work items" skill successfully performs the change without enforcing or prompting for mandatory custom fields defined in the Field Configuration of the destination issue type. This allows issues to exist in a state that violates project configuration requirements.

Steps to Reproduce

1. Identify or create a custom field (e.g., "Kev Severity Value") and set it as Required in the Field Configuration for the "Bug" issue type.
2. Open a "Story" issue that does not have this field populated.
3. Use Rovo Chat or a Rovo Agent and provide a prompt to change the issue type of that Story to a Bug. (e.g.: "convert ABC-123 into bug")
4. Observe that Rovo completes the update successfully.

Expected Results

Rovo should either prompt the user to provide the required field value or fail the operation with an error indicating that mandatory fields are missing, consistent with Jira's native "Move" or "Change Type" UI.

Actual Results

Rovo changes the issue type to "Bug" but leaves the required "Kev Severity Value" field empty, bypassing the Field Configuration requirement.

Workaround

Users should manually move the work item from Story to Bug using the Jira UI to ensure all required fields are captured and validated.