Skip to content
Notis

Check GitHub PR merge status daily for active Jira work

Some pull requests just quietly go stale. Once a day, Notis reviews the GitHub pull requests behind your active tickets and tells you which ones still have not merged, so nothing lingers unnoticed.

Trigger

Recurring schedule

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

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

PRs that never get merged fall out of sight, and you only notice when a ticket has been stuck for a week.

  • Surfaces stalled pull requests before they block a release
  • Gives you a predictable daily pulse instead of random surprises
  • No need to remember to audit open work yourself

Setup

Build it in a few focused steps.

  • 1Connect Jira and GitHub to Notis one time in the portal.
  • 2Open Automations in the portal and choose New Automation.
  • 3Describe it plainly: each morning, check whether the GitHub pull requests for my active Jira tickets have merged and list the ones that have not.
  • 4Pick a recurring schedule as the trigger and choose a channel for the daily report.
  • 5Run the automation once manually to confirm the summary looks right.

Questions about this workflow

How often does it run?

On whatever recurring schedule you set, such as every weekday morning.

Does it need a Jira event?

No. This runs on a schedule, so the trigger is a recurring timer rather than a Jira event.

What exactly does it report?

For each relevant PR, GitHub confirms merged or not merged, and Notis summarizes the unmerged ones for you.

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.

TriggerInstant

Accept a repository invitation

Accepts a pending repository invitation that has been issued to the authenticated user.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

List stargazers

Deprecated: lists users who have starred a repository; use `list stargazers` instead.

ActionInstant

Star a repository for the authenticated user

Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.