Docs
WebsiteLoginFree Trial
  • Getting Started
    • OnCall Users
    • Team Admins
    • Account Admins
  • Architecture Guide
  • Common UI Design Patterns
  • Alerts
  • Teams
  • Schedules
  • Escalation Policies
  • Integrations
  • Broadcasts
  • Users
  • Notifications
  • Reports
  • Billing
  • Accounts
  • Stakeholders
  • Maintenance Windows
  • Routers
  • Notification Rules
  • Single Sign On (SSO)
  • Integration Guides
    • Introduction
    • 66uptime
    • Apex Ping
    • AppDynamics
    • Auvik
    • AWS CloudWatch
    • Azure Monitor
    • Cloudflare
    • Cronitor
    • Datadog
    • Dead Man's Snitch
    • Echoes HQ
    • ElastAlert
    • Email
    • Form
    • Freshdesk
    • Freshservice
    • Google Hangouts Chat
    • Grafana
    • Healthchecks.io
    • HetrixTools
    • Honeybadger
    • Hydrozen
    • Jira Server
    • JotForm
    • Kapacitor
    • LogicMonitor
    • Mattermost
      • Outgoing Webhook
      • Post to Channel
    • Meta Workplace
    • Microsoft Teams
    • New Relic
    • Outgoing Webhook
    • Pingdom
    • Prometheus
    • PRTG Network Monitor
    • Pulsetic
    • Sentry
    • ServerGuard24
    • Site24x7
    • Slack
      • Notifications
      • Outgoing Webhook
      • Post to Channel
    • SolarWinds
    • Stackdriver
    • StatusCake
    • Twilio
      • Incoming SMS
      • Live Call Routing
    • Typeform
    • Uptime
    • Uptime Kuma
    • UptimeRobot
    • Webhook
    • Zendesk
  • API
    • Introduction
    • Authentication
    • Errors
    • Pagination and Filters
    • Common Model Attributes
    • Account Users
    • Alerts
    • Broadcasts
    • Comments
    • Escalation Policies
    • Events
    • Integrations
    • Logs
    • Maintenance Windows
    • Notification Rules
    • Routers
    • Schedules
    • Teams
    • Users
  • Command Line Interface (CLI)
    • PagerTree CLI: Command Line Interface
Powered by GitBook
On this page
  • What is Jira Server?
  • How It Works
  • Integration Walkthrough
  • In PagerTree
  • In Apex Ping

Was this helpful?

  1. Integration Guides

Jira Server

Connect your Jira Server issues to PagerTree.

PreviousHydrozenNextJotForm

Last updated 1 year ago

Was this helpful?

Company
Estimated Time
Vendor Docs
Open Source

5 minutes

What is Jira Server?

is an application that helps agile teams plan, track, and release great software.

How It Works

Jira Server creates issues.

  • When an issue in Jira Server is created, an alert is created in PagerTree automatically.

Integration Walkthrough

In this integration tutorial we will show you how to send issues from Jira Server into PagerTree. The estimated time for this integration is 5 minutes. We assume that you already have a PagerTree and Jira Server account/server setup.

In PagerTree

  1. by clicking the Jira Software logo.

  2. .

In Apex Ping

  1. Navigate to the Jira administration console under the main menu: Jira Software -> Settings -> System -> Advanced -> Webhooks. If you know your server url, webhooks can be found at the following path: <Jira Server URL>/plugins/servlet/webhooks

  2. In the upper right hand corner, click the Create a Webhook button.

  3. On the create webhook form, fill out the following:

    1. Name - An appropriate name (ex: “PagerTree Webhook Listener”)

    2. Url – Paste the PagerTree Endpoint URL you copied earlier

    3. Issue Related events

      1. Check Issue Created

    4. Click “Save” button.


You have successfully completed the Jira Server Integration.


Atlassian
view
v3.rb
Jira Server
In Jira, navigate to WebHooks.
Jira PagerTree Webhook Configuration
Jira Webhooks
Jira PagerTree Webhook Configuration
Create the integration
Copy the Endpoint URL