-
Bug
-
Resolution: Fixed
-
Medium
-
Severity 2 - Major
-
2,803
-
| 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
- Ensure that the test site has a lot of data/issues/projects
- 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:
- is duplicated by
-
-
- Closed
-
- blocked by
-
STLR-896 Failed to load
- is related to
-
JST-859360 You do not have permission to view this issue
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDCLOUD-14486] JQL query in SLA threshold breached trigger can often timeout
| Remote Link | New: This issue links to "Page (Confluence)" [ 980440 ] |
| Component/s | Original: Trigger - SLA [ 71691 ] | |
| Component/s | New: Trigger - SLA [ 76106 ] | |
| Key |
Original:
|
New:
|
| Project | Original: Automation for Cloud [ 22610 ] | New: Jira Service Management Cloud [ 18512 ] |
| Remote Link | Original: This issue links to "Page (Confluence)" [ 710469 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 858078 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 800787 ] |
| Remote Link | Original: This issue links to "Page (Confluence)" [ 796613 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 796613 ] |
This SLA issues were fixed about 2 days back through a case I reported. Finally they figured the issue.
We're happy to announce the bug is now fixed! Your patience and support during this period were invaluable. Our sincere apologies for any inconvenience caused.
If you still face the timeout error for SLA threshold automation rules, please raise a support ticket for it.