Issue Summary

When a Rovo agent uses the `Raise Request` tool to create a JSM request, and the target request type has a form with fields that are {}linked to Jira issue fields{} (i.e., the form field maps to a native Jira field), the agent enters an infinite confirmation loop. The `Raise Request` confirmation box keeps cycling because the agent cannot resolve what values to populate for those linked Jira fields.

Impact: Customers using Rovo agents to automate JSM request creation are blocked when their request types use forms with required Jira-linked fields. This directly impacts Rovo agent adoption.

Root cause: The `Raise Request` tool is unable to resolve or understand what values to populate for form fields that are linked to Jira issue fields. This is a known limitation confirmed by the leading engineer.

Steps to Reproduce

1. Create a JSM request type with a form that includes one or more fields linked to Jira issue fields (e.g., a field mapped to a native Jira field such as Priority, Assignee, etc.).
   2. Mark one or more of those linked fields as {}required{}.
   3. Configure a Rovo agent with the `Raise Request` tool.
   4. Ask the Rovo agent to raise a request of that type.

Multiple loom recording present for the same.

Expected Results

The Rovo agent should either: - Successfully populate the linked Jira fields and raise the request, OR - Gracefully inform the user that it cannot fill in the required linked fields and ask for manual input.

Actual Results

The `Raise Request` confirmation dialog loops repeatedly. The agent exhausts its loop limit trying to determine what values to supply for the linked Jira fields and never successfully raises the request.

Workaround

• Remove forms from request types that the Rovo agent needs to raise.
• Keep the forms but remove any fields that are linked to a Jira issue field.
• Keep the linked fields but remove the "required" constraint so the agent can skip them.