Version 1.0.4-a

[Improvement] Date pickers conform to configured date format

[Improvement] Reschedule maintenance automatically populates original date and time

[Improvement] Increased width for history filter drop down

[Bug] Fixed team member join form validation

 

Version 1.0.4

[Feature] User tracking for incident and maintenance updates

[Improvement] Enhanced redundancy to mitigate S3 outages for static assets and customer hosted images

[Improvement] Refactored cache invalidation process to mitigate S3 outages

[Improvement] Subscriber total value no longer factors in any pending subscribers

 

Version 1.0.3

[Improvement] Added a setting to change the container label displayed in incidents and maintenances

[Bug] Fixed container location bug that caused the location to be automatically set in certain circumstances

[Bug] Fixed stats widget calculation for upcoming maintenances

[Bug] Fixed custom subdomain setting issue for subdomains containing dashes

[Bug] Fixed team member invite join issue that allowed the email addresses to be modified

 

Enhanced Container Layouts

Containers are displayed below each component on a status page. The containers represent data centers, physical locations, cloud providers or any other grouping that makes sense for your unique system.

When we launched Status.io, containers were displayed in a vertical list below each component. Since then, we’ve experimented with different layouts and observed how our customers were customizing their status pages to learn more about the optimal display.

To make it easier to modify the container layout, we’ve released a new design setting to choose the layout thats works best for you. Choose to display containers in either horizontal, vertical or vertical expanded layouts.

Check out the examples below to see each layout in action.

 

Horizontal Layout

 

Vertical Expanded Layout

 

Vertical Condensed Layout

 

Modify the container layout from the Design/Advanced tab in the Dashboard. Learn more about container display options in our Knowledge Base.