Forums

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

Need help adding a custom action button (Promote to Jira) in Opsgenie alerts

Balaji G
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!
September 17, 2025

Background: Built automation to promote OpsGenie alerts to Jira tickets with single-click functionality for sandbox environment.

Technical Implementation (Working):

  • Created AWS Lambda function with Python code that processes OpsGenie webhooks
  • Successfully maps OpsGenie alert fields to Jira required fields
  • Handles field mapping:
  • Includes safety mode, duplicate prevention, error handling
  • Lambda function tested successfully, creates tickets with proper formatting
  • Function URL

OpsGenie Configuration Attempts:

  1. Created "Alert to JIRA" webhook integration (active and working)
  2. Created "Jira Integration Channel" action channel (Rest Endpoint type)
  3. Created "Promote to Jira" custom action in team settings
  4. Configured integration alert filters with "Custom alert action is executed"
  5. Attempted API integration approach as alternative

Current Issue: Despite proper configuration, the "Promote to Jira" button does not appear in OpsGenie alert interface. Lambda automation works perfectly when triggered manually, but custom action button is not visible to users on alerts.

 

1 answer

0 votes
Aditya Bodke
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 18, 2025

Hi Balaji,
Thank you for reaching out on Atlassian Community!

 

Custom Action Must Be Defined on the Alert or via Policy

  • The custom action (e.g., "Promote to Jira") must be explicitly defined on the alert itself or through alert policies. If the action is not attached to the alert, the button will not show. 

  • Here's how you can define an alert policy since it's the easiest, follow the screenshot
  • In this case, a Tag has been placed called Jira, so only alerts that come in with tag Jira will see this option. You can modify the tag name based on your requirement. 

Screenshot 2025-09-19 at 11.38.00 AM.png

  • Now, when a new Opsgenie alert that has been created that contains the tag Jira, the policy has been applied and the custom action will be available.

Screenshot 2025-09-19 at 11.42.45 AM.png

 

Hope this information helps!

 

Regards,
Aditya

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events