Check GitHub vulnerability reporting when a Jira security ticket is filed
A security ticket lands and the first question is always the same: is private vulnerability reporting even on for that repo? When the ticket is created in Jira, Notis checks the GitHub repository and tells you, so you start from facts.
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
Check private vulnerability reporting status
Checks if private vulnerability reporting is enabled for the specified repository.
Why this helps
Security tickets arrive without context, and manually checking each repository's vulnerability reporting status is a slow first step every time.
- You start every security ticket knowing the repo's reporting status
- Skips a repetitive manual lookup at the worst possible moment
- Creates a clear record of posture checks in your run channel
Setup
Build it in a few focused steps.
- 1Connect Jira and GitHub to Notis once in the portal.
- 2Open Automations in the portal and select New Automation.
- 3Describe the outcome: when a security ticket is created in Jira, check whether private vulnerability reporting is enabled on the named GitHub repository.
- 4Choose the New Issue trigger from Jira and set a channel for run reports.
- 5File a test security ticket and read the status Notis reports.
Questions about this workflow
What does the check tell me?
It reports whether private vulnerability reporting is enabled for the specified repository.
Can I scope this to security tickets only?
Yes. Your plain-language instruction defines which tickets qualify.
Does it change any settings?
This rule reads the status. You can extend the instruction if you want follow-up actions.
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.