NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist, #2117 most downloaded on Packagist
JIRA REST API Client for PHP Users.
Latest stable
5.16.1
Last release 17 days ago
05 Nov 2026
Ships fairly regularly
a new release about every 4 months
Some releases are documented
notes for 35 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
12 years old
157 releases · first in 2015
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
application configuration to a .env.
application configuration to a .env.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
fixed broken NoOperationMonologHandler changed by AbstractProcessingHandler return type definition.
JqlQuery::quote() now escapes backslashes (#230)quote('a\nb') produced the JQL escape sequence \n, and other backslashes caused illegal JQL escape sequence errors.\ becomes \\). If you relied on passing JQL escape sequences through quote(), build that part of the query yourself.Set OAUTH_ACCESS_TOKEN (or oauthAccessToken in ArrayConfiguration), and it is sent as Authorization: Bearer {token}. It takes precedence over the personal access token and basic authentication.
JIRA_HOST to https://api.atlassian.com/ex/jira/{cloudId}.The library only sends the token. Getting and refreshing it is up to your application. OAuth 1.0a is not supported.
Text search (~) treats characters like ( ) : / [ ] + - ! ^ ~ * ? as special syntax, so searching for a log line failed with Unable to parse the text.
JqlQuery::quoteText() escapes them, and addTextSearchExpression() uses it:
$jql = (new JqlQuery())
->addTextSearchExpression(JqlQuery::FIELD_SUMMARY, 'session_start(): Failed (path: /var/lib/php)');
// or with a raw JQL string
$jql = 'summary ~ '.JqlQuery::quoteText($text);quoteText() disables wildcards like *. Keep using quote() if you need them.
JqlQuery::quote() broke values containing a double quote (#230). It produced \\" instead of \".
Transition by untranslated status name (#323): Transition::setUntranslatedName() never worked.
IssueStatus didn't declare untranslatedName, so the value was dropped.findTransitonIdByUntranslatedName() returned the status id instead of the transition id, so the transition request failed.It now returns the transition that leads to the matched status. This works regardless of the user's language on Jira Cloud. Jira Server/Data Center doesn't provide untranslatedName, so there the status name is compared instead. The same fix applies to ServiceDesk\Request\RequestService.
AbstractConfiguration::getOAuthAccessToken() threw a TypeError when no token was configured.
JIRA_LOG_ENABLED, JIRA_LOG_FILE, JIRA_LOG_LEVEL) and the Laravel log location are documented in the README (#169).Full Changelog: 5.14.0...5.15.0
Atlassian Rovo MCP
Organization admins can now let service accounts connect to the Atlassian MCP server using OAuth 2.0 client credentials. Pipelines and scheduled jobs get an access token without a browser sign-in, and you don’t need to turn on API token authentication for your organization.
To get started with this change:
In Atlassian Administration, select your organization if you have more than one.
Go to Directory, then Service accounts, and create a service account. Give it app roles only on the sites it needs.
Select the service account, then Create credentials and OAuth 2.0.
Select the Product *:agent-interface scopes, plus read:me and read:account . You can’t change scopes after you create the credential.
Copy the client ID and client secret. The secret is shown only once.
In your workflow, exchange the client ID and secret for an access token, then send it to https://mcp.atlassian.com/v2/mcp as a Bearer token. Access tokens are valid for 60 minutes, so request a new one before the current one expires.
To create the credential, see Create an OAuth 2.0 credential for service accounts .
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.