Problem
Why are worklogs created through a Jira Model Context Protocol (MCP) server missing Tempo mandatory work attributes, and why aren't the required attribute validations being enforced?
Solution
Worklogs generated via a Jira MCP server use the native Jira REST API under the hood and function identically to logging time directly in Jira core. Because these requests interact directly with Jira rather than through Tempo's API, Tempo's custom validations, including mandatory work attributes, are completely bypassed.
Tempo does not have the technical authority or permission layer to intercept, validate, or block worklog creation requests made directly through Jira's native REST API or Jira core screens.
To enforce validation or restrict unvalidated time entry via external integrations, the policy must be implemented at the Atlassian Jira platform level, in order to resolve it please contact Atlassian Support