

“It is all very much part of devops and bringing more automation and less manual steps,” Azoff said. “Jira Ops is more out-of-the-box and has a lot of those features already created, rather than the user having to manipulate the tool to create workflows and so on. “Jira is a very flexible tool, so it can be molded for any type of user – including ops,” he said. Creating a tailored version of Jira makes sense for users, he said. The IT ops market represents a significant opportunity for Atlassian, said Michael Azoff, a principal analyst at Ovum. For example, PagerDuty or OpsGenie can automatically create an incident in Jira Ops to kick off a response, while dedicated Slack channels can be opened instantly to discuss a response.

Using Jira workflows, some response and resolution processes can be automated. The Jira Ops timeline also provides an overview of events, allowing new responders to get quickly updated. IT teams can still rely on Slack, for example, while Jira Ops provides visibility into what is going on in each platform, serving as an incident command center. The idea is not that it will replace other tools outright, but will integrate with them. It is available only as a cloud tool, with no plans to provide an on-premise version.
#CRITICAL OPS TRELLO FOR FREE#
Atlassian plans to offer Jira Ops for free as an early access product ahead of a version 1.0 release in early 2019.
