Opsgenie functionality ported to jira:// #1273
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Related issue (if applicable): #1272
JIRA API support added to allow those who used Opsgenie to continue to do so after Atlassian's acquisition of it.
Syntax
The syntax is as follows:
jira://{apikey}/
jira://{apikey}/@{user}
jira://{apikey}/@{user1}/@{user2}/@{userN}
jira://{apikey}/*{schedule}
jira://{apikey}/*{schedule1}}/*{schedule2}/*{scheduleN}
jira://{apikey}/^{escalation}
jira://{apikey}/^{escalation1}/^{escalation2}/^{escalationN}
jira://{apikey}/#{team}
jira://{apikey}/#{team1}/#{team2}/#{teamN}
Note: If no prefix character is specified, then the target is presumed to be a user (an
@
symbol is presumed to be in front of it).You can also mix/match the targets:
jira://{apikey}/@{user}/#{team}/*{schedule}/^{escalation}
Parameter Breakdown
username
,email
, oruuid4
. This is the assumed default target type to notify, but it is advised you prefix all users with a@
symbol to eliminate any ambiguity.uuid4
associated with it.Note: Teams must be prefixed with a
#
symbol.uuid4
associated with it.Note: Schedules must be prefixed with a
*
symbol.uuid4
associated with it.**Note:**Escalations must be prefixed with a
^
symbol.us
if not specified. Europeans must set this toeu
to work correctly.Note: This was ported over from the legacy Opsgenie plugin for backwards compatibility, but t this time this switch does not change anything.
3
if not specified.New Service Completion Status
%global common_description
Checklist
flake8
)Testing
Anyone can help test this source code as follows:
Include Details (Key/Value Pairs)
Jira allows you to provide details composed of key/value pairs you can set with messages. This can be accomplished by just sticking a plus symbol (+) in front of any parameter you specify on your URL string.