Atlassian’s Jira is an issue and project tracking software that helps plan, track and manage projects. Jira is also used by customers and internal teams to log issue tickets for the product and engineering teams to look into and resolve. This forms a feedback loop between the customer-facing and product teams to help drive and deliver the best possible software. Jira is widely adopted by Agile development teams to customize workflows and embrace collaborative resolutions to ship good software fast.

The coronavirus (COVID-19) pandemic has forced many global enterprises to temporarily shut down their operations, resulting in lost productivity and revenue losses. Yet, with a business continuity management (BCM) strategy, enterprises are well-equipped to limit business interruptions until the pandemic passes.

The unexpected and sudden shift to remote working introduces a new set of problems within the incident response space. And while each organization needs to take its own unique circumstances into account, this post outlines the best practices and steps that can be taken in the right direction in keeping operations both productive and proactive.

A Network Operations Center (NOC) is a location from which IT support technicians can supervise, monitor, and maintain client networks and infrastructure. Because they act as a central nervous system for many organizations, NOCs are typically located in a central physical location. The global coronavirus (COVID-19) pandemic is an unprecedented situation that is creating new challenges for everyone—and that includes NOCs.

COVID-19 is forcing many teams into crisis mode, as they rush to meet customer and employee needs in our new socially distanced reality. Organizations with experienced crisis management teams are urgently adding capacity and adapting to distributed working models. And those who haven’t built crisis response teams before are grappling with how to rapidly train employees and get access to the right tools.

Ever since the release of our Teams Integration blog we have received requests from customers on whether we can provide the same functionality for Slack. And the use cases actually are very similar – it is always about an efficient and pragmatic approach to logging issues and tickets that came up during the night by leveraging existing infrastructure and without adding more clutter.

No, it won’t be possible to continue operating business-as-usual. For the unforeseeable future, teams across the world will be dealing with cutbacks, infrastructure instability, and more. However, with SRE best practices, your team can embrace resilience and adapt through this difficult time.

Today, we are excited to announce PagerTree now officially supports schedule rotations! A long awaited feature and requested by many customers, with schedule rotations it’s now easier than ever to schedule a list (or “rotation”) of people for full coverage support. Schedule rotations are available on our Pro and Elite pricing plans and are technically a subset of our “recurring schedules” feature.

In today’s chaotic digital sphere, networks are distributed across an increasingly wide range of hackable endpoints. From smartphones and tablets to Internet of Things (IoT) devices—everything gets connected to the network. EDR technologies and practices were created for the purpose of providing active endpoint protection and defense. However, if your systems and admins are overloaded with alerts, an EDR strategy might become obsolete.

A lot of teams are asking us about how to do incident management when you’re suddenly remote. We understand. Going remote can be scary, and few things are scarier than having a service outage you aren’t prepared for. Nobody wants to be in a situation where an important service is going down and the engineer who can help isn’t answering on Slack. And if your company isn’t used to working remotely, it can be harder than ever to be on the same page during an incident.