Add GitHub labels automatically when a Jira ticket is created
You open a Jira ticket, then forget to go label the GitHub issue that mirrors it. Notis closes that gap: the second a ticket lands in your project, it reads the intent and applies matching labels on GitHub so triage stays consistent.
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
Labels on GitHub drift out of sync with Jira because nobody remembers to update them by hand, and untagged issues slip past triage.
- Keeps GitHub triage labels aligned with Jira without any manual tagging
- Removes the constant back-and-forth between two tools you already juggle
- Makes sure no new work item ships to engineering untagged
Setup
Build it in a few focused steps.
- 1Connect Jira and GitHub to Notis once from the portal integrations page.
- 2Ask Notis to send your portal link, then open Automations and choose New Automation.
- 3Write the instruction in plain language, for example: when a new Jira issue is created, add matching labels to the related GitHub issue.
- 4Pick the New Issue trigger from Jira and choose a channel where Notis reports each run.
- 5Create one real Jira ticket to confirm the GitHub labels appear as expected.
Questions about this workflow
Do I have to map Jira fields to GitHub label names?
No. You write one plain-language instruction and Notis interprets which labels fit. There are no field-mapping screens.
Which Jira issues trigger this?
Only issues created in the Jira project you select when you pick the New Issue trigger.
Will it create labels that do not exist yet?
Yes. If a label is not already in the repository, GitHub creates it as part of the action.
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.