I’m trying to set up automatic status transitions in Jira when Jenkins builds complete successfully. My goal is to move tickets from “Open” status to “Resolved” when the build passes.
JQL query: project=MYPROJ and issue=TICKET-123 and status=Open
Workflow action: “Resolved”
Build failure on JQL error: enabled
The Problem:
When Jenkins runs the build, I get this validation error:
Jira could not execute your JQL: com.atlassian.jira.rpc.exception.RemoteValidationException
Query validation failed: The value 'MYPROJ' does not exist for the field 'project'.
An issue with key 'TICKET-123' does not exist for field 'issue'.
The strange thing is that when I test the exact same JQL query directly in Jira’s issue navigator, it works perfectly and returns the expected results.
Has anyone encountered similar authentication or permission issues with the Jira Issue Updater plugin? What could be causing this discrepancy between the plugin’s JQL execution and Jira’s native query interface?
yeah, it really seems like a permissions thing. maybe Jenkins doesn’t have the right access to MYPROJ, even tho you do. double-check the service account’s browse permissions and make sure it can see TICKET-123.
Had the exact same problem with our Jira 6.1 setup last year. The SOAP service handles permissions differently than the web interface - even if your account can run the JQL in the browser, SOAP checks permissions at a lower level and might choke on your project key format. Switch to using the project ID number instead of the key (you’ll find it in project admin). That “issue key doesn’t exist” error tells me your JQL’s probably too restrictive. The plugin tries to validate everything upfront, so if TICKET-123 isn’t there right then, the whole query bombs. Pass the issue key as a parameter instead of hardcoding it - way more reliable.
The SOAP endpoint might be your problem. Jira 6.1 had authentication quirks where the plugin would connect but not get full user permissions. I’ve seen this before - the plugin authenticates but doesn’t inherit the complete user context. Switch to REST API if your Jenkins plugin supports it: https://MyJiraInstance/rest/api/2/. Also check your JQL syntax. Some plugins are way pickier about field references than Jira’s native interface. Since it works in the issue navigator but fails through the plugin, you’re authenticating but with limited permissions.