Add GitHub status check contexts when a Jira release ticket is created
Release prep should tighten your branch protection, not wait on you to remember it. When a release ticket appears in Jira, Notis adds the required status check contexts on GitHub so the gates are in place before merge time.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
Add status check contexts
Adds status check contexts (provided in the request body, e.g., `{"contexts": ["new-context"]}`) to a protected branch, requiring these contexts to have been previously reported.
Why this helps
Release checklists say add the required checks, but that manual step gets skipped under deadline pressure and risky merges slip through.
- Required checks are enforced before the release crunch begins
- Takes a fiddly, easy-to-forget admin step off your checklist
- Consistent gates on every release ticket, not just the ones you remember
Setup
Build it in a few focused steps.
- 1Connect Jira and GitHub to Notis once in the portal.
- 2Open Automations in the portal and select New Automation.
- 3Write the instruction: when a release ticket is created in Jira, add the required status check contexts to the protected branch.
- 4Choose the New Issue trigger from Jira and pick a channel for run reports.
- 5Create a test release ticket and confirm the status checks appear on GitHub.
Questions about this workflow
Do the checks need to exist already?
Yes. GitHub requires that the status check contexts have been reported before they can be added to a protected branch.
Which branch does it protect?
The branch you name in your plain-language instruction, with no configuration screens.
Can I limit this to release tickets?
Yes. Your instruction describes which tickets qualify, and Notis interprets that.
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.