Confirm a GitHub PR merged when a Jira ticket is closed
A ticket says done, but did the code actually ship? When a Jira ticket moves to done, Notis checks the linked GitHub pull request and tells you whether it truly merged, so closed does not quietly mean unmerged.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
Check if pull request merged
Checks if a specified github pull request has been merged, indicated by a 204 http status (merged) or 404 (not merged/found).
Why this helps
Tickets get marked done while their pull requests are still open, and the mismatch only surfaces when something is missing in production.
- Catches done tickets whose code never actually merged
- Gives you a quiet safety net instead of a production surprise
- Keeps your definition of done honest across both tools
Setup
Build it in a few focused steps.
- 1Connect Jira and GitHub to Notis once from the portal.
- 2In the portal, open Automations and start a New Automation.
- 3Write the instruction: when a Jira ticket is marked done, check whether the linked GitHub pull request has merged and report the result.
- 4Choose the Updated Issue trigger from Jira and set a channel for the run report.
- 5Move a test ticket to done and read the merge-status message Notis sends.
Questions about this workflow
What does the check return?
GitHub confirms merged or not merged, and Notis relays that plainly in your chosen channel.
Does this reopen the ticket if the PR is not merged?
This rule reports the status. You can extend the instruction to alert you or take further action.
Which ticket updates trigger it?
Updates to issues in your selected Jira project, acted on when the status becomes done.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to GitHub. A trigger fires from one place; an action lands in another.
Jira triggers
GitHub actions
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
New Project
Triggered when a new project is added in Jira
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Not just Jira and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.