We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

       

      Product Update - 28th June 2023
      Hi folks,
      Thank you for your patience on this issue. Long term fix for this issue has been implemented and will be gradually rolled out in the coming weeks. 

       

      Product Update - 18th Jan 2023
      Hi folks,
       
      This request is now under development. I will share an update on the timelines once we have it. 
       
      If you are facing difficulty setting up SLAs (due to limits, conditions, goals etc.) and would be interested in talking to product team and provide feedback, you can book a slot using this link.
       
      https://calendly.com/manas-atlassian/30-min-customer-meeting  
      Product Update - 9th Nov 2022
      Hi folks,
       
      This request has been prioritised and would soon be picked up by our development team. Once we have a timeline, I'll update it here.
       
      If you are facing difficulty setting up SLAs (due to limits, conditions, goals etc.) and would be interested in talking to product team and provide feedback, you can book a slot using this link.
       
      https://calendly.com/manas-atlassian/30-min-customer-meeting  

      Issue Summary

      The SLA trigger can often timeout when performing a JQL query to see which issues had past the given threshold. This prints the error SocketException: Socket closed to the audit log (Besides the error 'SocketException: Socket closed' the audit log can also print the errors: 'Service Unavailable' and 'Internal server error').

      • Current implementation relies on polling - product teams should look at using native events instead to improve reliability
      • Attempting to retry queries in the case of timeout to minimise errors might be a short term option

      Steps to Reproduce

      1. Ensure that the test site has a lot of data/issues/projects
      2. Configure an automation rule with a SLA threshold breached trigger - allow the rule to run

      Expected Results

      • Rule runs without issues

      Actual Results

      • Rule randomly fails with "SocketException: Socket closed"(or similar) message
      • The rule query fails due to timeout

      Workaround

      • Use the legacy automation rules - "SLA time remaining" trigger can be used:

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

                 

                Product Update - 28th June 2023
                Hi folks,
                Thank you for your patience on this issue. Long term fix for this issue has been implemented and will be gradually rolled out in the coming weeks. 

                 

                Product Update - 18th Jan 2023
                Hi folks,
                 
                This request is now under development. I will share an update on the timelines once we have it. 
                 
                If you are facing difficulty setting up SLAs (due to limits, conditions, goals etc.) and would be interested in talking to product team and provide feedback, you can book a slot using this link.
                 
                https://calendly.com/manas-atlassian/30-min-customer-meeting  
                Product Update - 9th Nov 2022
                Hi folks,
                 
                This request has been prioritised and would soon be picked up by our development team. Once we have a timeline, I'll update it here.
                 
                If you are facing difficulty setting up SLAs (due to limits, conditions, goals etc.) and would be interested in talking to product team and provide feedback, you can book a slot using this link.
                 
                https://calendly.com/manas-atlassian/30-min-customer-meeting  

                Issue Summary

                The SLA trigger can often timeout when performing a JQL query to see which issues had past the given threshold. This prints the error SocketException: Socket closed to the audit log (Besides the error 'SocketException: Socket closed' the audit log can also print the errors: 'Service Unavailable' and 'Internal server error').

                • Current implementation relies on polling - product teams should look at using native events instead to improve reliability
                • Attempting to retry queries in the case of timeout to minimise errors might be a short term option

                Steps to Reproduce

                1. Ensure that the test site has a lot of data/issues/projects
                2. Configure an automation rule with a SLA threshold breached trigger - allow the rule to run

                Expected Results

                • Rule runs without issues

                Actual Results

                • Rule randomly fails with "SocketException: Socket closed"(or similar) message
                • The rule query fails due to timeout

                Workaround

                • Use the legacy automation rules - "SLA time remaining" trigger can be used:

                        8a3861d8a88c Manas Shukla
                        dnguyen4 Derrick Nguyen
                        Votes:
                        346 Vote for this issue
                        Watchers:
                        309 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            8a3861d8a88c Manas Shukla
                            dnguyen4 Derrick Nguyen
                            Affected customers:
                            346 This affects my team
                            Watchers:
                            309 Start watching this issue

                              Created:
                              Updated:
                              Resolved: