Pharos Hotfix for Jira Cloud Integration Now Available

You may see Jira errors or ticket creation issues — disconnect temporarily if affected.

We’re happy to share that the Pharos hotfix for Jira Cloud integration is now available for installation. This update resolves the recent issues caused by Atlassian’s unexpected Jira Cloud API deprecations, which temporarily affected ticket creation and caused Jira-related errors in some users’ logs.

What’s fixed

  • Restored full functionality for “Create Ticket” and ticketing automation rules

  • Resolved Jira-related log errors tied to deprecated endpoints

  • Improved resilience for future Atlassian API changes

How to install

You can install the hotfix directly from the following links:

No additional steps are required after installation — your Jira Cloud integration will resume normal operation automatically.

Upgrade timeline

We encourage you to apply the update at your earliest convenience.
If you prefer to wait, the hotfix will be automatically deployed as part of our maintenance schedule starting October 31st.

No downtime is expected, and no configuration changes will be needed after the update.

Reporting Issues

While we constantly perform rigorous testing of our application during all stages of development, we simply cannot test in your org. Each Salesforce organization is unique in its configuration and usage. Therefore, It is important to double check your Logs tab as soon as you can!

Note: Timing is key. If you were experiencing issues before the date of this upgrade, they’re likely unrelated to the upgrade itself. We still want to hear about them, but understanding the context will help us address your concerns more efficiently.

Things to look out for

  1. Pharos errors — these are Logs with Pharos Category. These indicate potential problems with the Pharos managed package. If you started seeing these errors after the upgrade, do let us know!

  2. Incomplete data on Log or Issue records. If you notice something is missing in your logs post upgrade, such as: lack of visual debug views, lack of environment data, or even lack of log records themselves, definitely let us know!

  3. Broken integrations. If you notice lack of notifications, Jira/ADO tickets, or changes in your GitHub change tracking repository post upgrade, please give us a holler!

  4. Any other issues. The list above reflects the most common problems our customers may face. It is by no means exhaustive, however. If you are unsure whether the problem you started seeing is upgrade related, let us know anyway and we’ll help you investigate.

How to report problems

  1. Send an email to [email protected] providing your Salesforce Organization Id, any screenshots or necessary details in the email. Please also include Maintenance Release in the subject.

  2. Create a case via our support portal with any screenshots or details, as well as the following information:

Release Notes

Pharos maintenance releases typically address known or reported bugs. However, we will sometimes include small functionality enhancements as well.

Bugfixes

Jira search projects endpoint deprecation (LOG-2652)

Impacts: Jira Integration

Build Azure DevOps integrations with Microsoft Entra OAuth apps (LOG-2656)

Impacts: Azure DevOps Integration

Teams integration issue (LOG-2649)

Impacts: MS Teams Integration