Release Notes: September 2021
NEW! Release Note Enhancements 09/09/2021
Inclusion of Ticket IDs (JIRA / Support) to enhance Customer experience using the Release Notes.
Bug Fixes 09/09/2021
Impact time validation ignores time zone (EN-4053 / ZD-159)
Issue: If you edit the start time of an incident and try to set it beyond the “base” datetime (not including the time zone designation), the UI gives an error like "Datetime should be lower than 2021/07/21 07:00 PM".
Fix: The issue was caused by looking at the “raw” time and not the time in the provided time zone. Now, Blameless adjusts to a common time zone to be able to compare the values accurately.
Incident Update API called in Infinite Loop at high throughput (EN-3921)
Issue: In some cases, the Incident Update API call could cause recurring API calls, resulting in the web UI becoming unresponsive.
Fix: Added verification logic to prevent a high frequency loop from starting or interrupt it if it did.
Token Expired
appearing for users when logging into Blameless (EN-3985 / ZD-129)
Issue:
Customers would frequently see spurious “token is expired” error messages in the lower right corner of the web UI. These were misleading messages being generated. There were no token issues actually occurring.
Incident Update API called in Infinite Loop at high throughput (EN-3921)
Issue: In some cases, the Incident Update API call could cause recurring API calls, resulting in the web UI becoming unresponsive.
Fix: Added verification logic to prevent a high frequency loop from starting or interrupt it if it did.
Token Expired
appearing for users when logging into Blameless (EN-3985 / ZD-129)
Issue:
Customers would frequently see spurious “token is expired” error messages in the lower right corner of the web UI. These were misleading messages being generated. There were no token issues actually occurring.
Fix: Validate if a token issue is actually occurring; if not, ignore.These misleading messages should not show up any more.
Required task inaccessible after being assigned to role (not user); blocks incident closure (EN-3952 / ZD-66)
Issue: If a Required task was assigned to a Role (such as “Tech Lead”) and not to the user to whom the role was assigned, the task was inaccessible, blocking the ability to close the Incident in question.
Fix: Fixed the assignment logic to correctly accept a Role or a User.
Incidents have odd dates in Slack mobile view (EN-3947)
Issue: The Incident rundown message in Slack was showing the incident times incorrectly in Slack mobile.
Fix: The Date/Time element was delivering ambiguous values to the Slack API. The fix was to disambiguate the time format being used.
PDF file attached as event from web UI fails to load (EN-3051)
Issue: After attaching a PDF file to an incident or retrospective, whenever a user would try to view the file, they would receive the following error:
Failed to load PDF document.
=======
Incidents have odd dates in Slack mobile view (EN-3947)
Issue: The Incident rundown message in Slack was showing the incident times incorrectly in Slack mobile.
Fix: The Date/Time element was delivering ambiguous values to the Slack API. The fix was to disambiguate the time format being used.
PDF file attached as event from web UI fails to load (EN-3051)
Issue: After attaching a PDF file to an incident or retrospective, whenever a user would try to view the file, they would receive the following error:
Failed to load PDF document.
Fix: Fixed the metadata Mime-Type label to correctly retrieve PDF files which have been attached.
Custom question answers were not being saved after a forced refresh, possibly due to expired token (EN-4086 / NA)
Issue: When the user supplies answers to the custom questions, if they are forced to refresh the screen, the answers do not save.
Fix: Blameless now preserves the answers across sessions.
Comments
0 comments
Please sign in to leave a comment.