Jira


Schemes	`jira://`, `opsgenie://`
Cargo feature	`service-jira`
Service	https://atlassian.com/
Body formats	`text` (first is the default)
Attachments	no
Title length	250 characters
Body length	15,000 characters
Body lines	unlimited
Request throttle	none
Vendor URLs accepted	no

URL formats

{schema}://{apikey}
{schema}://{user}@{apikey}
{schema}://{apikey}/{targets}
{schema}://{user}@{apikey}/{targets}

{schema} is one of jira://, opsgenie://.

URL tokens

Token	Meaning	Type	Required	Notes
`{apikey}`	API Key	string	yes	secret
`{target_escalation}`	Target Escalation	string	no	prefix `^`
`{target_schedule}`	Target Schedule	string	no	prefix `*`
`{target_team}`	Target Team	string	no	prefix `#`
`{target_user}`	Target User	string	no	prefix `@`
`{targets}`	Targets	list	no	any of `target_escalation`, `target_schedule`, `target_team`, `target_user`; separated by `/`
`{user}`	Username	string	no

Query parameters

Parameter	Meaning	Type	Default	Notes
`action`	Action	choice	`map`	one of `map`, `new`, `close`, `delete`, `acknowledge`, `note`
`alias`	Alias	string
`batch`	Batch Mode	bool	`no`
`entity`	Entity	string
`priority`	Priority	choice	`3`	one of `1`, `2`, `3`, `4`, `5`
`region`	Region Name	choice	`us`	one of `us`, `eu`
`tags`	Tags	string
`to`	Targets	list		sets `{targets}`

Prefixed parameters:

+name=value: Details
:name=value: Action Mapping

The common URL parameters (format, overflow, verify, redirect, cto, rto, retry, wait, store, tag, tz, user, password, port, optional, emojis) apply as well.

Examples

Accepted URLs (tokens are fake):

jira://k3/
jira://user@k2/
jira://k13b/@user?:s=
jira://k21/?action=new
jira://k17/user@email.com/#team/*sche/^esc/%20/a?action=new
jira://k12/@user?action=close
jira://k6/@user?region=EU&action=new
opsgenie://k6/@user?region=EU&action=new

Rejected URLs:

jira://
jira://:@/
jira://%20%20/
jira://k1/user/?region=xx

Send one from the command line:

mercurio -t 'Backup' -b 'Finished in 42s' 'jira://k3/'

Notes

Jira Service Management (jira://, opsgenie://): creates and manages alerts through the JSM Operations alert API.

opsgenie:// URLs land here too: Opsgenie shuts down on 2027-04-05 and its alert API lives on unchanged as JSM Operations (api.atlassian.com/jsm/ops/integration/v2/alerts, GenieKey auth).

The requestIds of created alerts are kept in the persistent store (60 days) so later close/acknowledge/note/delete actions act on them.

Differences with Apprise

opsgenie:// URLs are sent by the jira service to Jira Service Management Operations (Apprise posts them to api(.eu).opsgenie.com, which shuts down on 2027-04-05); the key must come from a JSM Operations API integration. ?region=eu no longer changes the host.

Keyboard shortcuts