Sync GitHub issue labels when a Jira ticket status changes
Your Jira board says in review, your GitHub issue still says todo. Notis keeps them aligned by updating the GitHub labels each time the Jira status moves, so anyone reading either board sees the truth.
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
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
GitHub labels freeze at whatever they were, while the real state lives in Jira, so the two boards constantly contradict each other.
- Both boards reflect the same status without manual upkeep
- Teammates reading GitHub see current state, not stale labels
- You stop being the human sync between two tools
Setup
Build it in a few focused steps.
- 1Connect Jira and GitHub to Notis once in the portal.
- 2Open Automations from the portal and choose New Automation.
- 3State the outcome plainly: when a Jira ticket's status changes, update the status labels on the linked GitHub issue to match.
- 4Pick the Updated Issue trigger from Jira and select a run-report channel.
- 5Change one ticket's status and confirm the GitHub labels follow.
Questions about this workflow
Will old status labels be replaced?
Your instruction can describe swapping the old status label for the new one so the issue never shows two states.
Does a comment on the ticket trigger it?
No. The Updated Issue trigger does not fire on comment activity, only on field changes like status.
Do I list every status manually?
No. You describe the intent once and Notis interprets each status change without a 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
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.