Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

OpsgenieからJiraSMへの移行について

植村 吉博
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 23, 2025

OpsgenieからJiraSMへの移行にあたり、チャットツールの引継ぎは
Opsgenieの統合とJiraSM側統合と同期(Opsgenie側でJiraSMを使用し
ていたので)を確認して同じなら問題ないか
また、Opsgenie側にアクションとインシデントルールがなかった場
合、JiraSM側に作成する必要はない認識でいいか

1 answer

0 votes
Eugenio Onofre
Community Champion
May 1, 2025

Hi @植村 吉博

When migrating from Opsgenie to Jira Service Management (JSM), here are a couple of clarifications:

If your chat tool integration (e.g., Slack, MS Teams) is configured the same way in both Opsgenie and JSM (same channels, similar notification triggers), there’s typically no issue continuing with the setup in JSM. However, since JSM and Opsgenie can differ in how they send and format notifications, it's a good idea to review and test the JSM-side integration independently, just to ensure consistency in behavior.

As for Action and Incident Rules, if there were no custom action rules or incident rules defined in Opsgenie, there's generally no need to replicate them in JSM, unless you're planning to introduce new automations or escalation logic.

Still, if you're planning to use JSM for incident response or on-call management, it may be worth reviewing:

  • Incident issue type settings and workflows
  • Automation rules for incident creation or notification
  • Any integrations with services, components, or asset objects

Please remember to vote and accept this answer in case it helps you resolve this issue.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events