February 20
API
Admin Portal
Integrations
Subscribers
Beacons
Incident Management
February 20
[closed]
New
- Added API support for creating and managing Content Templates
- Added API support for using a content template when creating an incident through the API
- Added API support for creating subscribers in bulk
- New API for bulk group action POST
- New API for bulk group action DELETE
- Added support for sending notifications to multiple MS Teams channels at once
- Updated the MS teams card layout to be more visually informative
- Allow ANY incident or event to be posted in the future and have it automatically resolve itself
- New admin alert for if we fail to send SMS to a custom Twilio account
- For sandbox accounts added a label to appear and help users know they are in their sandbox account
- Updated the logic for the Unsubscribe macro to take subscribers to their subscription management page
- Added support to fill in Full Name for subscribers in the admin dashboard and subscription management page
Fixed
- IncidentUpdate.InDirectlyAffectedComponentsByName macro was not populating correctly
- Posts created by beacons were not being drafted if the overall incident was
- A subscribers "Tags' would be cleared when they set or reset their password
- Importing subscribers gives Employee Role, despite subscriber role selection prior to import
- Publish button in confirmation modal allows you create duplicate incident
December 26
Admin Portal
Notifications
Integrations
Subscribers
Services/Components
Status Page
Incident Management
December 26
[closed]
New
- Importing contacts via CSV now updates existing subscribers instead of overwriting them
- Added a From Name option to all email integrations
- Using an accounts Company name as the From name when sending emails
- Upcoming maintenance in dashboard expanded to list up to 5
- Content templates allow for setting the Post Type
- Added the title of an incident to Slack Incident Management notifications
- Expanded the Help Center link in the admin portal to provide additional resources and contact details for StatusCast's support team
Fixed
- Uptime SLA report graph did not always project the right periods based on the date range
- Admin Notifications sometimes contained a link with extra '/login' or '/admin' appended
- Uptime calculation allowed rounding the final result if over the .995% threshold
- Google translate did not work on the headers of the incident page viewed from a status page
- Maintenance Lock does not prevent component status change through the API
- Service Report does not show any of the components that are set to be treated as cloud components
- Manage subscription page after SMS confirmation can cause the phone field to get cleared out
- Manual component statuses that are ongoing are not represented on the service status list or history grid widget
- RSS feed time zone abbreviation not conforming to RFC-822
November 15
Admin Portal
Subscribers
Beacons
Services/Components
Status Page
November 15
[closed]
New
- Add enhanced logic to beacons NOT using external ID to check for open incidents by components
- Add support for default email templates per action(new, updated, resolved)
- Add group ID to group settings UI
- Add 'Duration' column to incidents page
Fixed
- RSS feed using the incorrect timezone
- Incident Creation: when adding a URL link, the submit button is not showing text (or background is white)
- Manager role: should not see the Page Designer link in the admin menu
- Components won't let you update with the SLA thresholds set to 0
- Incident summary: when submitting an informational or future maintenance it says on going
- Drafting an event does not retain the affected components
- Maintenance events plotted on the calendar seem to be plotted based on estimated duration only
October 27
Groups
API
Admin Portal
Integrations
Subscribers
Status Page
Incident Management
October 27
[closed]
New
- New option to force the selection of components when creating an incident
- New option to force the selection of groups when creating an incident
- Updated the public status page new subscription modal to require component selection
- Added the year to the "Last Login" details for administrative user
- Added a disable option to beacons to allow beacon processing to be turned off
- Added an option to Beacon extract components to allow you to stop processing if no match is found
- New timeline entry for when NO notification channels were selected when publishing a post
- Logic added to determine an incidents minimum role based on lowest role of selected components
- Updated the automatic page-refresh to support 1 minute refreshes
- Added the duration property to API results for resolved incidents
- Added capability to search content templates when applying them in posts
- Expanded third party cloud provider beacons to allow group assignments(manual and automated)
Fixed
- When "Treat information posts as incidents?" is disabled editing the start date is not adjusting the auto-closure time
- Admins created through SSO login continued to show the "Pending" status on their user profile
- SSO integrations allowed you to save empty configurations
- History grid widget collapsing components when set to expand on load
- Incidents API throwing the duplicate date/time error if the PUT endpoint included the original post
August 21
Groups
Admin Portal
Notifications
Integrations
Subscribers
Services/Components
Status Page
Incident Management
August 21
[closed]
New
- Reintroducing Post Types! Set an additional property on any post that gives users an idea of what your team is doing
- New Incident Timeline providing more context to administrators regarding post creation, management, authors, etc...
- New notification filter option to combine group and component subscriptions
- Upload a CSV file to select Affected Groups and save your admins more time!
- New subscriber management for groups
- New URL shortener implemented for SMS notifications links
- New RCA Brand Template available
- New Component Status Change Brand Template available
- Paging added to Incident List widget for pages that want to show more than 10 incidents at a time.
Fixed
- Selecting publish when components are expanded UI
- Subscriber export includes empty group data
- When using SSO, going to the "view incident" link in admin/reports/incidents makes you log in with ID/pwd
- Slack Notifications missing component names
- Update Incident Templates not applying component status
- Inconsistent group alphabetization throughout the admin portal
- Drag and drop components not working
- When a cloud incident is created and resolved at the same time the status of the component stays affected
August 08
Groups
Admin Portal
Beacons
Services/Components
Status Page
Incident Management
August 08
[closed]
New
- Added beacon ruleset capability to the Internal Status Beacon type.
- Added Group selection to Content Templates
- Add the Estimated Duration of a maintenance to the incident workspace
- Added macro support for StatusPage.CurrentIncidentUrl in the HTML and Header widgets
- Added macro support for StatusPage.CurrentIncidentTitle in the HTML and Hedaer widgets
Fixed
- Incident History page sometimes shows incorrect number of paged results
- Groups are not alphabetically listed to admins after an incident is created
- Status page uptime history report off by 1 day when using custom range selector
- Service status list when using tabbed roots and status sorting would incorrectly reorder the tabs by status
- Service status list when sorted by status had investigating, monitoring, and identified out of order
- Unable to save child components whose parents are set to hidden
- Account font not being pre-selected in editor
- Future maintenance events that start at 12:00AM did not appear on the history grid until resolved
- The New Subscription brand template getting sent instead of the New User type
June 27
API
Admin Portal
Notifications
Integrations
Beacons
Services/Components
June 27
[closed]
New
- Add display for number of groups/components to incident form and workspace
- Added new GET Component Uptime API endpoint
- Added new Get multiple Components Uptime API endpoint
- Added an option to allow SSO created subscriptions to be setup to get email notifications by default.
- Added a new "Select all" option to the component selector when creating incidents and searching for components
- Added a Default font and Font Size option to the Style and Design settings
Fixed
- Internal status page beacon: when an incident is resolved on the main page, the incident on the internal page is not updated
- Incident API was not returning Affected Components that had a minimum role higher than "Everyone"
- Admin notification links were not accounting for accounts with SSO setup
- Admin notification emails filtered out affected components with a role set higher than "Everyone"
- Beacon escalation alerts continued to go off after a beacon has been acknowledged
June 02
Admin Portal
June 02
[closed]
Fixed
- Editing an existing post and save throws the error that you have a duplicate post time
- Creating an identified incident using a template results in an "Informational" event type instead of "Incident"
May 31
Groups
API
Admin Portal
Status Page
May 31
[closed]
New
- New Get Group Components API endpoint
- New Put Group Components API endpoint
- New Get Group Incidents API endpoint
- New Put Group Incidents API endpoint
- New Get Group Subscriptions API endpoint
- New Put Group Subscriptions API endpoint
Fixed
- Service list widget was not populating incident data when hovering over ongoing incidents
- Incident resolutions being allowed at the same minute interval as a previous update
- Pre-selected time when adding a post update was based on the time of the page load
- When drafting an informational event(that is not treated like an incident) the automated closure was not being set to a draft
May 19
Admin Portal
Integrations
Subscribers
Status Page
May 19
[closed]
Fixed
- Custom field macro listed separating values with commas instead of new lines
- Subscribers who never logged in, show last login as 1/1/0001
- Webex teams notifications not getting delivered
- Service status list widget using history using UTC to determine when "today" starts
- Authenticating for the first time as an "Employee" role through OpenID Connect fails
- Status pages that are set to private are not enforcing that subscribers also have accounts created
NO RESULTS