Open an issue on a confirmed outage
The issue is created once enough independent EU locations fail the check often enough in a row, both thresholds sit in your package, not on the first failed request.
Use Uptimeify with Jira.
An API token and a project key, and every confirmed outage becomes a ticket in the board your team already grooms. Nobody has to type it.
What lands in Jira
Everything the alert pipeline creates in Jira is on this list, and nothing beyond it. Read it once and you know what your team will see.
File the recovery as its own issue
The all clear arrives as a second issue naming the site that is back and how long it was gone, and the outage issue stays where it is.
Set the priority from the severity
An outage or a slow site becomes High, a warning or a flapping site Medium, and a recovery Low.
Raise a failing certificate to Critical
Once a TLS certificate crosses into its critical window the issue is filed at Critical, above the priority the event alone would give it.
Label and type every issue
Each issue carries the labels uptimeify and monitoring, in the issue type you picked when you set the channel up.
Describe what happened
URL, customer, organisation, the error with its status code, the checking locations and the times all sit in the description.
A project per client
Each channel carries its own base URL and project key, so a client's outage lands on the board the people who look after that client actually read.
File a test issue
The dashboard creates one issue marked TEST while you set the channel up, so a wrong project key is caught before the first outage.
Keep the API token encrypted
The Atlassian token authenticates over the REST API and is stored encrypted rather than as plain text.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
1. Take your Jira base URL
The base URL is the root of your Atlassian instance, the yourcompany.atlassian.net address you sign in at.
API token
ATATT3xFfGF0...Stored encrypted
2. Create an API token
On id.atlassian.com go to Security, then API tokens, and create the classic token without scopes. A scoped token talks to api.atlassian.com, not to your site address.
3. Name the project in Uptimeify
Add base URL, email, token, project key and issue type as a Jira channel, assign the monitors it covers, and file the test issue.
Before you connect Jira.
No. The recovery is filed as its own issue rather than closing the first one, so the outage keeps its history, its comments and whatever workflow state your team moved it to.
The one you name on the channel, Bug unless you choose otherwise. The project key decides the project, so different clients can go to different boards.
No. Your quota covers monitors and the monthly SMS and voice allowance. Issues created in Jira, GitHub or GitLab do not draw on it.
A certificate that has reached its critical window does, filed at Critical. Blocklist hits and domain expiry reminders stay on the chat and paging channels, where a ticket per reminder would be noise rather than work.
No. An issue is created for the confirmed outage, not per failed request, and how many re-checks confirmation takes is yours to set per package.
Atlassian gives new tokens a year by default, 365 days at most. A lapsed token shows up as a failed delivery on the channel rather than as silence, so put the renewal in the calendar the day you create it.
Every alert, where your team already works.
Connect Jira once, and every confirmed outage arrives as a ticket on the board your team already grooms.