May <var data-var='date'>12</var>, <var data-var='time'>12:04</var> UTC Resolved - This incident has been resolved. App is functioning in Ohio region correctly again. May <var data-var='date'>12</var>, <var data-var='time'>10:52</var> UTC Identified - During the deployment of the new version, a problem with app packages a version mismatch caused by CI/CD pipeline caused failure. Team identified the problem and is fixing the problem.

Time to SLA: partial outage in Ohio region

Apr <var data-var='date'>28</var>, <var data-var='time'>08:19</var> UTC Resolved - The migration to Forge is complete, and the app is operating normally for all customers. Apr <var data-var='date'>27</var>, <var data-var='time'>08:30</var> UTC Update - The migration to Forge has been completed. We will continue to monitor the application closely to confirm stability. Apr <var data-var='date'>25</var>, <var data-var='time'>08:47</var> UTC Monitoring - Rich Filters for Jira Dashboards is moving to Atlassian's Forge platform over several few days. The app is expected to work normally throughout this period. However, a very small number of customers with strict firewall settings reported outages due to the new application domain being blocked. If your organization uses a network security solution, you may need to allowlist *.atlassian-dev.net to maintain access. Please check our documentation for details: https://support.appfire.com/space/RFCDOC/3171189121 You can also reach out to support at: https://support.appfire.com/page/support

Rich Filters migration to Forge

Apr <var data-var='date'>21</var>, <var data-var='time'>17:25</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>21</var>, <var data-var='time'>17:12</var> UTC Monitoring - Performance has stabilized, and error rates have returned to normal levels. We are monitoring to ensure the app remains stable as we investigate the long-term resolution for this traffic pattern. Apr <var data-var='date'>21</var>, <var data-var='time'>16:15</var> UTC Investigating - We are currently investigating an increase in latency and intermittent errors within Comala Document Management. This is due to a sudden surge in database requests that has exceeded our current autoscaling thresholds. Our engineering team is actively working to scale our infrastructure manually to stabilize performance.

Comala Document Management - Degraded Performance

Apr <var data-var='date'> 9</var>, <var data-var='time'>08:17</var> UTC Resolved - We have confirmed that the upstream delivery issues have been fully resolved. The backlog of delayed events has been processed, and our systems are once again synchronizing Jira issue creations and updates in real-time. Apr <var data-var='date'> 8</var>, <var data-var='time'>17:21</var> UTC Monitoring - We are seeing event processing times start to return to normal, though it may take a bit more time for the backlog to fully clear. We are closely monitoring delivery rates and will mark this incident as resolved once we confirm all events are consistently arriving without delay. Apr <var data-var='date'> 8</var>, <var data-var='time'>13:57</var> UTC Identified - We are currently experiencing degraded performance regarding the synchronization of Jira issues. You may notice delays of up to 20 minutes between an action occurring in Jira (such as creating or updating an issue) and that change reflecting in our system. Impact Summary: What is affected: Real-time synchronization of Jira issues. What is NOT affected: No data is being lost. All events are safely queued and will be processed as soon as they are delivered to our system. Who is affected: This is currently impacting all customers utilizing our app, particularly those hosted in the EU and DE regions. Root Cause: This delay is stemming from an ongoing upstream degradation with Atlassian's webhook delivery systems. We are actively monitoring Atlassian's status and are in direct contact with their developer support team to expedite a resolution.

Time to SLA - Delayed Jira Issue Synchronization

Apr <var data-var='date'> 6</var>, <var data-var='time'>06:02</var> UTC Completed - The scheduled maintenance for the Connector for Salesforce & Jira has been successfully completed. All services are now fully operational. Thank you for your patience and support during this maintenance window. If you experience any issues, please reach out to our support team. Apr <var data-var='date'> 6</var>, <var data-var='time'>05:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>30</var>, <var data-var='time'>14:13</var> UTC Scheduled - We have a scheduled maintenance window for the Connector for Salesforce & Jira. Maintenance Details: Date: April 06, 2026 Time: 5:00 A.M. (UTC) Duration: Approximately 2 hours This maintenance will help us ensure the app’s performance and reliability. During this time, you may experience brief disruptions or downtime. We apologize for any inconvenience and appreciate your understanding. We will update here with the status, once the maintenance has been completed. Thank you.

Connector for Salesforce & Jira - Scheduled Maintenance

Mar <var data-var='date'> 6</var>, <var data-var='time'>14:04</var> UTC Resolved - After an extended observation period, we have confirmed that the implemented changes have successfully mitigated the issue. Performance remains stable, and the incident is now closed. Jan <var data-var='date'>13</var>, <var data-var='time'>13:01</var> UTC Monitoring - Atlassian has provided a fix for API rate limiting from Jira platform. We are continuing our talks with Atlassian and monitoring the systems. Jan <var data-var='date'> 9</var>, <var data-var='time'>10:14</var> UTC Identified - Time to SLA is currently experiencing degraded performance caused by elevated API rate limiting from Jira platform. We are in contact with Atlassian to understand the root cause of rate limiting and mitigate the problem.

Time to SLA: Degraded performance

Feb <var data-var='date'> 6</var>, <var data-var='time'>11:42</var> UTC Resolved - This incident has been resolved. Time to SLA and the Forge platform are now operating normally. Feb <var data-var='date'> 6</var>, <var data-var='time'>11:27</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb <var data-var='date'> 6</var>, <var data-var='time'>19:39</var> UTC Identified - The issue has been identified and a fix is being implemented by Forge platform. Feb <var data-var='date'> 6</var>, <var data-var='time'>11:01</var> UTC Investigating - Time to SLA is currently experiencing a partial outage caused by an issue with Forge scheduled triggers. We are actively monitoring the situation and are awaiting a fix from the Forge platform team. https://developer.status.atlassian.com/incidents/rlrntm2fw82b

Time to SLA – Partial Outage due to Forge Scheduled Triggers

Dec <var data-var='date'>22</var>, <var data-var='time'>10:15</var> UTC Completed - The scheduled maintenance has been completed. Dec <var data-var='date'>22</var>, <var data-var='time'>09:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Dec <var data-var='date'>22</var>, <var data-var='time'>09:23</var> UTC Scheduled - We will be performing scheduled maintenance on 2025-12-22 between 09:30 and 10:15 UTC. The service will be temporarily unavailable. We will update once completed.

Scheduled Maintenance

Dec <var data-var='date'>16</var>, <var data-var='time'>12:45</var> UTC Completed - The scheduled maintenance has been completed. Dec <var data-var='date'>16</var>, <var data-var='time'>12:15</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Dec <var data-var='date'>16</var>, <var data-var='time'>11:28</var> UTC Scheduled - We will be performing scheduled maintenance on 2025-12-16 between 12:15 and 12:45 UTC. The service will be temporarily unavailable. We will update once completed.

Nov <var data-var='date'>19</var>, <var data-var='time'>14:42</var> UTC Resolved - Dear Users, We are pleased to inform you that TFS4JIRA for Azure DevOps is now fully operational. Key Information: - The User Interface is now fully accessible, and all functions have returned to normal. If you have any questions or concerns, please feel free to reach out to our support team. We apologize once again for any inconvenience caused during the downtime and appreciate your patience and understanding. Thank you, and have a great day! Best regards, The TFS4JIRA Team Nov <var data-var='date'>19</var>, <var data-var='time'>12:55</var> UTC Monitoring - Dear customer, We are pleased to inform you that TFS4JIRA is now fully operational. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding. Our team is continuing to monitor the system closely. We will provide further updates as needed. If you have any questions or require assistance, please don’t hesitate to reach out to our support team—we’re here to help. Thank you for your continued trust in TFS4JIRA. Best regards, The TFS4JIRA Team Nov <var data-var='date'>19</var>, <var data-var='time'>11:32</var> UTC Identified - Dear Customers, TFS4JIRA for Azure DevOps user interface is currently not operational. Our team has identified the issue and is actively working to resolve it as quickly as possible. We will provide updates on the status page as we make progress and notify you once the service is fully operational again. Impact: - User Interface Access is unavailable We apologize for the disruption and appreciate your patience. If you have any questions or need further clarification, please feel free to reach out to our support team—we are here to assist you. Thank you for your continued trust in TFS4JIRA. Best regards, The TFS4JIRA Team

TFS4JIRA for Azure DevOps: Partial downtime

Jul <var data-var='date'>30</var>, <var data-var='time'>08:25</var> UTC Resolved - The incident resolved by Atlassian. Jul <var data-var='date'>23</var>, <var data-var='time'>08:25</var> UTC Update - We are continuing on waiting a fix from Atlassian. Jul <var data-var='date'>18</var>, <var data-var='time'>08:39</var> UTC Update - Atlassian approved the problem is caused by the Forge and created a incident of their own. https://developer.status.atlassian.com/incidents/8gwd2x0ql9l3 Waiting for fix from Atlassian. Jul <var data-var='date'>17</var>, <var data-var='time'>17:53</var> UTC Update - https://ecosystem.atlassian.net/servicedesk/customer/portal/34/ECOHELP-76209 has been progressed into 'In Progress' status around 4 hours ago, still waiting for further updates. Jul <var data-var='date'>17</var>, <var data-var='time'>12:50</var> UTC Identified - The problem seems to be the app user not having the correct permission in several instances. We are trying to find possible solutions as well as actions we can take. A ticket to Atlassian has also been submitted. Jul <var data-var='date'>17</var>, <var data-var='time'>10:17</var> UTC Investigating - We are currently investigating a problem where several instances are facing problems while trying to get the app properties from Jira REST API. No possible reason has been found, we have been able to reproduce it in one of the test environments we have.

Time to SLA partially facing problem with reaching `/application-properties` endpoint after CoF migration

Jul <var data-var='date'>18</var>, <var data-var='time'>15:00</var> UTC Resolved - On Friday around 14:57 UTC for about an hour we experienced the incident in the Canned Responses application. The issue was caused by a temporary database outage, which made the app unusable. Everything is now back to normal, we are currently working with a database supplier, so that such a problem does not repeat in the future. We apologize for any inconvenience caused during the downtime and appreciate your patience and understanding.

Canned Responses: Service Outage

Jun <var data-var='date'>17</var>, <var data-var='time'>12:04</var> UTC Resolved - Dear Customer, We’re pleased to share that the recent issue impacting TFS4JIRA has been fully resolved, and the system is now operating normally. Earlier today, a partial outage affected synchronization from Jira to Azure DevOps for a subset of our customers. Our engineering team quickly identified the root cause, implemented a fix, and we have since completed the monitoring period to confirm that all services are functioning as expected. We sincerely appreciate your patience and understanding during this incident. If you have any questions or notice any issues, our support team is ready to assist. Thank you again for your continued trust in TFS4JIRA. Best regards, The TFS4JIRA Team Jun <var data-var='date'>17</var>, <var data-var='time'>11:47</var> UTC Monitoring - Dear Customer, Earlier today, TFS4JIRA experienced a partial outage that affected normal operations. Our team promptly identified the root cause and implemented a fix. We’re happy to confirm that TFS4JIRA is now fully operational, and all synchronization activities have resumed. We are actively monitoring the system to ensure continued stability. We sincerely apologize for any inconvenience caused by this disruption and appreciate your patience and understanding throughout the incident. If you have any questions or require further assistance, please don’t hesitate to contact our support team—we’re here to help. Thank you for your continued trust in TFS4JIRA. Best regards, The TFS4JIRA Team Jun <var data-var='date'>17</var>, <var data-var='time'>09:44</var> UTC Identified - Dear Customer, TFS4JIRA is experiencing a partial outage that is affecting normal operations: Synchronization Service is facing an error during synchronization from Jira to Azure. Our team has already identified the issue and is taking immediate action to resolve it. We sincerely apologize for any inconvenience this may cause and appreciate your patience and understanding. We will provide further updates as needed. If you have any questions or require assistance, please don’t hesitate to reach out to our support team—we’re here to help. Best regards, The TFS4JIRA Team

TFS4JIRA for Azure DevOps - Partial Outage

May <var data-var='date'>21</var>, <var data-var='time'>09:00</var> UTC Completed - The scheduled maintenance has been completed. May <var data-var='date'>21</var>, <var data-var='time'>07:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'>16</var>, <var data-var='time'>09:07</var> UTC Scheduled - The application will be undergoing a scheduled maintenance during this time. The application will be unavailable during this time.

Scheduled application maintenance

May <var data-var='date'> 7</var>, <var data-var='time'>13:23</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 7</var>, <var data-var='time'>09:15</var> UTC Monitoring - The GCP incident has been resolved, Canned Responses Pro is back to normal function. The team keeps monitoring the situation. May <var data-var='date'> 7</var>, <var data-var='time'>09:02</var> UTC Identified - The issue has been identified and a fix is being implemented. May <var data-var='date'> 7</var>, <var data-var='time'>09:01</var> UTC Investigating - Due to an incident on Google Cloud Platform in eu-west3 region Canned Responses Pro users in Germany may be experiencing interruption of service. The team is investigating if the issue can be worked around.

Canned Responses Pro - interruption of service in DE region (eu-west3)

May <var data-var='date'> 7</var>, <var data-var='time'>11:30</var> UTC Resolved - Dear Users, We are pleased to inform you that TFS4JIRA for Azure DevOps is now fully operational. Key Information: - No synchronization data has been lost. - All synchronizations resumed automatically. If you have any questions or concerns, please feel free to reach out to our support team. We apologize once again for any inconvenience caused during the downtime and appreciate your patience and understanding. Thank you, and have a great day! Best regards, The TFS4JIRA Team May <var data-var='date'> 7</var>, <var data-var='time'>10:39</var> UTC Monitoring - Dear customer, We are pleased to inform you that TFS4JIRA is now fully operational. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding. Our team is continuing to monitor the system closely. We will provide further updates as needed. If you have any questions or require assistance, please don’t hesitate to reach out to our support team—we’re here to help. Thank you for your continued trust in TFS4JIRA. Best regards, The TFS4JIRA Team May <var data-var='date'> 7</var>, <var data-var='time'>08:55</var> UTC Identified - The TFS4JIRA for Azure DevOps is currently unavailable. Customers will experience issues performing key activities. Current Status: We have identified the root cause of the issue. It is related to an ongoing incident with our cloud provider. We are actively working with them to resolve the problem as quickly as possible. We apologize for the disruption and appreciate your patience. The next update will be provided in 2 hours or sooner. May <var data-var='date'> 7</var>, <var data-var='time'>08:04</var> UTC Investigating - The TFS4JIRA for Azure DevOps is currently unavailable. Customers will experience issues performing key activities. Current Update: We are aware of the outage affecting the app and are actively investigating the root cause. Our engineering team is working to restore full functionality as quickly as possible. We apologize for the disruption and appreciate your patience. The next update will be provided in 2 hours or sooner.

TFS4JIRA for Azure DevOps - Service Outage

Apr <var data-var='date'> 8</var>, <var data-var='time'>11:30</var> UTC Resolved - On 8th April 2025, Toggl encountered issues due to a gradual rollout of changes by Atlassian, which affected a portion of our customers. Issue has been resolved

Toggl: integration interrupted service

Mar <var data-var='date'>11</var>, <var data-var='time'>21:06</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>11</var>, <var data-var='time'>19:32</var> UTC Monitoring - Time to SLA app was down in the US region starting from 8 AM EST. The app was restored at 2 PM and we are currently monitoring the app.

Time to SLA: Outage in the US region

Feb <var data-var='date'>27</var>, <var data-var='time'>10:02</var> UTC Completed - The scheduled maintenance has been completed. Feb <var data-var='date'>27</var>, <var data-var='time'>09:21</var> UTC Verifying - Verification is currently underway for the maintenance items. Feb <var data-var='date'>27</var>, <var data-var='time'>08:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'>26</var>, <var data-var='time'>14:39</var> UTC Scheduled - Publisher for Confluence Cloud to Salesforce Maintenance Window: 2025-02-27 , 8AM to 10AM (UTC) Impact: The application may be intermittently unavailable during this time. We are performing a scheduled maintenance to enhance system reliability. During this period, users may experience temporary disruptions. Our team will work to minimize impact and restore full service as soon as possible. Thank you for your patience and understanding.

Scheduled System Maintenance

Feb <var data-var='date'>17</var>, <var data-var='time'>06:14</var> UTC Completed - The scheduled maintenance has been completed. Feb <var data-var='date'>17</var>, <var data-var='time'>05:49</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'>17</var>, <var data-var='time'>05:48</var> UTC Update - We will be undergoing scheduled maintenance during this time. Feb <var data-var='date'>17</var>, <var data-var='time'>05:47</var> UTC Scheduled - We are performing a scheduled maintenance on SFCC, resulting in a brief downtime. Maintenance Window: 17 Feb 2025 5:30AM - 7:30AM Expected Impact: SFCC will be temporarily unavailable during this period. We appreciate your patience and will work to minimize disruption. Thank you for your understanding!

Connector for Salesforce & Confluence Cloud (SFCC) Downtime - Scheduled maintenance

Feb <var data-var='date'>14</var>, <var data-var='time'>16:13</var> UTC Resolved - Dear Customer, We are pleased to inform you that TFS4JIRA for Azure DevOps is now fully operational. We apologize once again for any inconvenience this may have caused and appreciate your patience and understanding. If you have any questions or require assistance, please don’t hesitate to reach out to our support team—we’re here to help. Thank you for your continued trust in TFS4JIRA. Best regards, The TFS4JIRA Team Feb <var data-var='date'>14</var>, <var data-var='time'>12:57</var> UTC Update - Dear customer, We are pleased to inform you that TFS4JIRA is now fully operational, and all synchronization processes have resumed without interruption. Any initial synchronization processes that began before the outage are continuing as expected. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding. We will provide further updates as needed. If you have any questions or require assistance, please don’t hesitate to reach out to our support team—we’re here to help. Thank you for your continued trust in TFS4JIRA. Best regards, The TFS4JIRA Team Feb <var data-var='date'>14</var>, <var data-var='time'>12:50</var> UTC Monitoring - Dear Customer, Earlier today, TFS4JIRA experienced a temporary downtime that affected normal operations: - Synchronization Services encountered delayed requests when rendering data for approximately 15 minutes. Our team quickly identified the issue and took immediate action to resolve it. We are actively monitoring the system to ensure full stability. We are pleased to inform you that TFS4JIRA is now fully operational, and all synchronization processes have resumed without interruption. Any initial synchronization processes that began before the outage are continuing as expected. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding. We will provide further updates as needed. If you have any questions or require assistance, please don’t hesitate to reach out to our support team—we’re here to help. Thank you for your continued trust in TFS4JIRA. Best regards, The TFS4JIRA Team

TFS4JIRA for Azure DevOps - Partial Service Outage Notification

Feb <var data-var='date'>13</var>, <var data-var='time'>17:00</var> UTC Resolved - Dear Customer, Today, TFS4JIRA experienced a temporary downtime that impacted normal operations as follows: - Synchronization Services faced delayed requests when rendering data for approximately 5 minutes. - User Interface Access was partially unavailable for approximately 20 minutes. Our team quickly identified and resolved the issue, and we are pleased to inform you that TFS4JIRA is now fully operational. All synchronization operations have resumed without interruptions, including: - Any initial synchronization processes that started before the outage will continue execution as expected. - The User Interface is now fully accessible, and all functions have returned to normal. We sincerely apologize for any inconvenience this downtime may have caused and truly appreciate your patience and understanding. If you have any questions or need further clarification, please feel free to reach out to our support team—we are here to assist you. Thank you for your continued trust in TFS4JIRA. Best regards, The TFS4JIRA Team

Feb <var data-var='date'>11</var>, <var data-var='time'>09:35</var> UTC Resolved - Connector for Salesforce & Jira : Incident Resolved The service has remained stable following our monitoring period, and we are now marking this incident as resolved. Our team will continue conducting a detailed review to prevent future occurrences. We sincerely apologize for any disruption this may have caused and appreciate your patience. If you experience any further issues, please reach out to our support team. Feb <var data-var='date'>11</var>, <var data-var='time'>07:29</var> UTC Monitoring - Connector for Salesforce & Jira : Service Restored The service has been restored, and all functionality should now be operating normally. Customers may have experienced intermittent unavailability of the Connector for Salesforce & Jira. Our team is continuing to monitor system performance closely. We are also conducting a detailed investigation to determine the root cause and ensure long-term stability. We will continue monitoring for the next 2 hours, after which we will mark this incident as resolved if no further issues arise. We sincerely apologize for the disruption and appreciate your patience. If you are still experiencing any issues, please reach out to our support team. Feb <var data-var='date'>11</var>, <var data-var='time'>05:58</var> UTC Investigating - The Connector for Salesforce & Jira is currently intermittently unavailable. Customers may experience issues performing key activities. Current Update: We are aware of the outage affecting the app and are actively investigating the root cause. Our engineering team is working to restore full functionality as quickly as possible. We apologize for the disruption and appreciate your patience. The next update will be provided in 2 hours or sooner.

Connector for Salesforce & Jira: Service Outage

Jan <var data-var='date'> 9</var>, <var data-var='time'>13:16</var> UTC Resolved - Dear Users, We are pleased to inform you that TFS4JIRA for Azure DevOps is now fully operational. Key Information: - No synchronization data has been lost. - All synchronizations will resume automatically. If you have any questions or concerns, please feel free to reach out to our support team. We apologize once again for any inconvenience caused during the downtime and appreciate your patience and understanding. Thank you, and have a great day! Best regards, The TFS4JIRA Team Jan <var data-var='date'> 9</var>, <var data-var='time'>12:39</var> UTC Monitoring - Dear Users, We are pleased to inform you that TFS4JIRA for Azure DevOps is now operational, and we are monitoring it. Key Information: - No synchronization data has been lost. - All synchronizations will resume automatically. If you have any questions or concerns, please feel free to reach out to our support team. We apologize once again for any inconvenience caused during the downtime and appreciate your patience and understanding. Thank you, and have a great day! Best regards, The TFS4JIRA Team Jan <var data-var='date'> 9</var>, <var data-var='time'>12:07</var> UTC Identified - Dear Users, TFS4JIRA for Azure DevOps is currently not operational. Our team has identified the issue and is actively working to resolve it as quickly as possible. We will provide updates on the status page as we make progress and notify you once the service is fully operational again. Impact: - Synchronization between Jira and Azure DevOps will not occur during this downtime. - Normal operations will resume once TFS4JIRA is restored. We sincerely apologize for any inconvenience this may cause and thank you for your patience and understanding. Best regards, The TFS4JIRA Team

TFS4JIRA for Azure DevOps - Temporary Downtime

Dec <var data-var='date'>20</var>, <var data-var='time'>12:55</var> UTC Resolved - This incident has been resolved. Dec <var data-var='date'>20</var>, <var data-var='time'>10:31</var> UTC Update - The issue is fully resolved and the app is operational. Dec <var data-var='date'>19</var>, <var data-var='time'>14:53</var> UTC Monitoring - A fix has been implemented and released, we are monitoring the results now. Dec <var data-var='date'>19</var>, <var data-var='time'>12:50</var> UTC Identified - The team has identified the route cause of the issue - there was an unexpected change in Atlassian Connect JavaScript API behavior, breaking the logic behind switching between chats. The team is working on a hotfix, more updates to follow shortly. Dec <var data-var='date'>19</var>, <var data-var='time'>12:35</var> UTC Investigating - We are seeing issues with switching between issues/chat in the Chat Dashboard. The team is actively investigating the issue and will provide an update shortly.

Is Mohami down?

Mohami status is UP

Lastest published events

Time to SLA: partial outage in Ohio region

Rich Filters migration to Forge

Comala Document Management - Degraded Performance

Mohami Services, Components and Regions

Recent Mohami events

Time to SLA: partial outage in Ohio region

Rich Filters migration to Forge

Comala Document Management - Degraded Performance

Time to SLA - Delayed Jira Issue Synchronization

Connector for Salesforce & Jira - Scheduled Maintenance

Time to SLA: Degraded performance