Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Search the Community

Showing results for tags 'jira ops'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Categories

  • Organization
  • Leadership
  • Requirements
  • Design
    • User Experience
    • User Interface
  • Development
    • Frontend
  • Quality & Security
  • Deployment & Network
  • Atlassian
    • Jira
    • Confluence
    • Bitbucket
  • Wordpress
  • E-commerce

Categories

  • Project Manager
  • Process & Method Specialist

Calendars

  • Community Calendar
  • Organization Events
  • Leadership Events
  • Design Events
  • Development Events
  • Deployments Events
  • Requirement Events
  • Quality Events
  • Atlassian Events
  • Wordpress Events
  • Atlassian AUG Stockholm's Events

Forums

  • General Area
    • General Area
  • Areas of interest
    • Organization
    • Leadership
    • Design
    • Development
    • Deployment
    • Requirements
    • Quality
  • Special Areas
    • Atlassian
    • Wordpress
  • Atlassian AUG Stockholm's Diskussioner

Blogs

There are no results to display.

There are no results to display.

Categories

  • Files
  • Fonts
  • Presentations
  • Atlassian AUG Stockholm's Filer

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Found 1 result

  1. Modern incident management. One place to respond, resolve, and learn from every incident. Raise an incident in Jira Ops or through an integration with your alerting tool. Then fire up a chat room, alert additional responders, and publish initial comms all with a single button. This is Jira Ops. The features looks great and I especially like the connection between the different tools such as the new Jira Ops, that looks very much like ServiceDesk, that connects to StatusPage and Slack. Postmortem followup in Confluence would make it easy to reference in ServiceDesk in the event a similar incident happen again, or if a temporary fix has been setup. Jira Ops is now available for free, at least for now. The integrations looks good and the reports seems ok, but I did not see a SLA setup as we have in ServiceDesk and I would like to know how tasks are connected in case they need to be fixed by a developing team, or other teams using Jira for task management. Affected services are also a bit interesting since it's usually a pretty big database of hardware, software and services for big companies. I will add it to my own setup and play around with it to see how it works and what to expect of it. I like what I see so far though, how about you? Read more about Jira Ops on the Atlassian website.
here
×