Check GitHub issue assignability when a Jira ticket is reassigned
You move a ticket to a new engineer, but can they even be assigned on GitHub? When a Jira reassignment happens, Notis checks whether the new owner can take the linked GitHub issue and warns you if not, before the mismatch bites.
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
Check if a user can be assigned to an issue
Checks if a specified github user can be assigned to a given issue within a repository.
Why this helps
A Jira ticket gets reassigned to someone without GitHub access, and the broken assignment only surfaces later as silent confusion.
- Catches assignments to people who lack GitHub access early
- Avoids silent GitHub failures where the assignee never sticks
- Gives you a clear heads-up instead of a confusing gap
Setup
Build it in a few focused steps.
- 1Connect Jira and GitHub to Notis once in the portal.
- 2Open Automations in the portal and choose New Automation.
- 3Describe it plainly: when a Jira ticket is reassigned, check whether the new owner can be assigned to the linked GitHub issue and warn me if not.
- 4Select the Updated Issue trigger from Jira and pick a channel for run reports.
- 5Reassign a test ticket and read the eligibility result Notis sends.
Questions about this workflow
What confirms assignability?
GitHub confirms whether the user can be assigned to the issue, and Notis relays that plainly.
Does it assign them automatically too?
This rule verifies eligibility. You can combine it with an assign action in your instruction if you want.
Which changes trigger it?
Updates to issues in your chosen Jira project, acted on when the assignee changes.
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.