Skip to content
Notis

Grant GitHub team repo access when a Jira project is created

Kicking off a new project means the team needs the repo, and that admin step always lands on you. When a project appears in Jira, Notis sets the GitHub team's repository permissions so everyone can start on day one.

Trigger

New Project

Triggered when a new project is added in Jira

Action

Add or update team repository permissions

Sets or updates a team's permission level for a repository within an organization; the team must be a member of the organization.

Why this helps

Every new project restarts the same permissions chore, and the team waits while you remember to configure GitHub team access.

  • The right team gets repo access at project kickoff, not days later
  • Removes a repetitive admin task from your plate entirely
  • Access is consistent every time a project spins up

Setup

Build it in a few focused steps.

  • 1Connect Jira and GitHub to Notis once through the portal.
  • 2Open Automations in the portal and select New Automation.
  • 3Write it plainly: when a new Jira project is created, grant the matching GitHub team its repository permission level.
  • 4Choose the New Project trigger from Jira and pick a channel for run reports.
  • 5Create a test project in Jira and confirm the team permissions are set on GitHub.

Questions about this workflow

What permission levels can it set?

Your instruction can specify read, write, or admin, and Notis applies it for the organization team.

Does the team need to be in the organization?

Yes. GitHub requires the team to be a member of the organization for the permission to apply.

Do I map project names to teams?

No. You describe which team gets access in plain language, with no mapping screens.

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.

TriggerInstant

Accept a repository invitation

Accepts a pending repository invitation that has been issued to the authenticated user.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

List stargazers

Deprecated: lists users who have starred a repository; use `list stargazers` instead.

ActionInstant

Star a repository for the authenticated user

Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.