Add a priority label to GitHub when a Jira bug is created
Engineers on GitHub cannot see how urgent a bug is unless someone carries the priority over. When a bug is created in Jira, Notis adds the matching priority label to the GitHub issue, so the queue sorts itself by what matters most.
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 labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Bug priority lives in Jira, so engineers working from GitHub cannot tell a firefight from a nice-to-have without switching tabs.
- Engineers see urgency directly on the GitHub issue
- Priority triage stops requiring a trip back to Jira
- The queue naturally sorts by what needs attention first
Setup
Build it in a few focused steps.
- 1Connect Jira and GitHub to Notis once from the portal.
- 2Open Automations in the portal and select New Automation.
- 3Describe it plainly: when a bug is created in Jira, add its priority as a label on the linked GitHub issue.
- 4Choose the New Issue trigger from Jira and pick a channel for run reports.
- 5Create a test bug with a priority and confirm the GitHub label appears.
Questions about this workflow
Will it create the priority label if missing?
Yes. GitHub creates labels that do not already exist as part of the action.
Can I limit it to bugs only?
Yes. Your plain-language instruction defines which tickets count as bugs.
Do I map each priority value manually?
No. You describe the intent once and Notis interprets the priority, with no mapping table.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
New Project
Triggered when a new project is added in Jira
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for 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.
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.
Jira and GitHub, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business GitHub.