Add a GitHub collaborator when a Jira access ticket is created
A new contractor files an access ticket in Jira and then waits, and waits. Notis reads that ticket the moment it appears and adds the person as a collaborator on the right repository, so they can start today.
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 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.
Why this helps
Access requests pile up in Jira while people sit idle, because granting GitHub access is a manual task that always waits for a free moment.
- New hires and contractors get repo access without a waiting queue
- Access requests stop stalling in a backlog you have to remember to clear
- Every grant is logged in your run channel for an easy audit trail
Setup
Build it in a few focused steps.
- 1Connect Jira and GitHub to Notis one time in the portal.
- 2Open Automations in the portal and choose New Automation.
- 3Describe it plainly: when an access-request ticket is created in Jira, add the named person as a collaborator on the repository they need.
- 4Select the New Issue trigger from Jira and choose a channel for run reports.
- 5File one test access ticket and confirm the collaborator invitation is created.
Questions about this workflow
Can it set the permission level?
Yes. Your plain-language instruction can state the access level, which applies to organization-owned repositories.
Does this create an invitation or add them directly?
GitHub may create an invitation or update permissions directly, depending on the account, and Notis reports the outcome.
How does Notis know which repo?
It reads the repository from the ticket contents based on your instruction, with no manual field mapping.
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.