- Pharos Product Updates
- Posts
- Jira Cloud API Deprecation Impacting Pharos
Jira Cloud API Deprecation Impacting Pharos
You may see Jira errors or ticket creation issues — disconnect temporarily if affected. Hotfix arriving this week.
Dear Customer,
We wanted to make you aware of a recent change from Atlassian that may temporarily impact Jira Cloud integrations with Pharos.
Around this time last year, Atlassian quietly announced the deprecation of key Jira Cloud REST API endpoints, including those used by Pharos to perform JQL searches. Unfortunately, the timing and communication of this deprecation didn’t align with reality, creating confusion across the Jira ecosystem — including among partners and integration providers like us.
Important
If your organization uses Jira Cloud, please read the details below.
If you use Jira Server or Data Center (hosted Jira), you are not affected and no action is needed.
What this means for Jira Cloud users
Due to Atlassian’s deprecation, Pharos Jira Cloud integrations may experience intermittent errors in logs or lose certain functionality temporarily.
You may notice that:
Jira-related errors start appearing in your Pharos logs
You may not be able to create Jira tickets from Issues, either via the “Create Ticket” button or through ticketing automation rules
All other Pharos functionality remains unaffected.
What you can do
While it’s not mandatory to disable your Jira Cloud integration, if you begin seeing frequent Jira-related errors, we recommend temporarily disconnecting Jira to prevent unnecessary log noise:
Go to Pharos Admin → Integrations → Jira → Authentication
Click Reset to disconnect your Jira integration

We’re releasing a hotfix later this week to restore full compatibility with Atlassian’s updated API framework. After that, you’ll be able to reconnect your Jira Cloud integration seamlessly.
What’s next
Our engineering team is treating this with top priority and will notify you as soon as the fix is deployed. We’re also enhancing our upstream monitoring to better anticipate third-party API changes like this in the future.
We appreciate your patience and understanding as we work quickly to address this. If you need any help or have questions, please reach out to [email protected]