Summary

Testing of issue creation in Jira Service Management projects via the Atlassian Model Context Protocol (MCP) has identified a limitation regarding portal-based workflows. In environments where direct issue creation is restricted to enforce the use of Portal Forms, the current MCP implementation fails to create requests because it relies on standard Jira REST APIs rather than the JSM-specific portal request flow. This prevents the automation of issue creation in projects that require portal-only submissions for data integrity and validation.

Suggestion

Enhance the Atlassian MCP to support Jira Service Management Portal Request creation. This would involve:

• Simulating Portal Submissions: Allowing MCP to interact with the JSM-specific Request APIs (e.g., /rest/servicedeskapi/request) rather than just the standard Jira Issue API.

• Form Field Mapping: Enabling MCP to recognize and populate fields defined within JSM portal forms, including ProForma/Forms fields.

• Request Type Support: Ensuring that issues created via MCP are correctly associated with a specific JSM Request Type, allowing them to pass through portal-only validation and restrictions.