Update GitHub issue assignees when a Jira ticket is reassigned
Ownership shifts on a Jira ticket, but the GitHub issue still shows the old engineer. Notis watches for the change and moves the assignee on GitHub to match, so the right person always sees the work.
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 assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Reassignments happen in Jira but the GitHub issue keeps pointing at whoever picked it up first, so pings go to the wrong person.
- The right engineer is always assigned on GitHub without a manual handoff
- Cuts the confusion of two tools showing two different owners
- Notis reports each reassignment so you can trust it happened
Setup
Build it in a few focused steps.
- 1Connect Jira and GitHub to Notis a single time in the portal.
- 2Open Automations in the portal and start a New Automation.
- 3Describe the outcome plainly: when a Jira ticket's assignee changes, set the same person as the assignee on the linked GitHub issue.
- 4Select the Updated Issue trigger from Jira and pick a channel for run reports.
- 5Reassign one test ticket in Jira and confirm the GitHub assignee updates.
Questions about this workflow
Does this fire on every Jira change?
It fires on updates to issues in your chosen project. Notis only acts on the assignment when the instruction calls for it.
What if the person lacks push access on GitHub?
GitHub silently ignores assignee changes for users without push access, and Notis will note that in the run report.
Can it remove an old assignee too?
Yes. The add-assignees action can adjust the assignee list, which your instruction can describe.
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.