Automatically Create Tracking Tasks for All Pull Requests

A new pull request opens in GitHub. Notis creates a tracking task in Jira so the change stays visible.

Trigger

New Pull Request Created

Triggers when a new pull request is created in GitHub, matching the optional configured filters. Emits an event for each newly created pull request. Supports filtering by repository, owner/organisation, author, assignee, label, state, base branch, head branch, and draft status.

Jira logo

Action

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

Why this helps

Pull requests stay hidden in GitHub's PR tab until someone explicitly checks for them. You can't see the volume of in-flight work, and changes slip through without proper visibility or review scheduling.

  • Gain full visibility into all in-flight code changes
  • Track PR status in your primary task system
  • Ensure nothing slips through unreviewed
  • Build a historical record of all changes

Setup

Build it in a few focused steps.

  • 1Connect GitHub and Jira to Notis.
  • 2Tell Notis: 'When a new pull request is created, add a tracking task to Jira.'
  • 3Set trigger to 'New Pull Request Created' and action to 'Create Issue'.
  • 4Choose your Jira project and configure filters if needed (e.g., only certain repositories).
  • 5Test by opening a pull request and checking that the Jira task appears.

Questions about this workflow

Will draft PRs be tracked?

Yes, unless you configure the trigger to exclude drafts in your plain-language prompt.

What happens if a PR is closed without merging?

The Jira task remains. You can manually close it or add logic to auto-close matching Jira tickets.

Can I filter by repository or author?

Yes—configure the trigger to watch specific repositories or use your prompt to filter by author.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link GitHub to Jira. A trigger fires from one place; an action lands in another.

GitHub logo

GitHub triggers

Jira logo

Jira actions

New Workflow Artifact Created

Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.

TriggerPolling

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

Branch Changed

Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.

TriggerPolling

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

Add Watcher to Issue

Adds a user to an issue's watcher list by account id.

ActionInstant

Check Run Status / Conclusion Changed

Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.

TriggerPolling

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

ActionInstant

Check Suite Status / Conclusion Changed

Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.

TriggerPolling

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

ActionInstant

New Code Scanning Alert Created

Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.

TriggerPolling

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

ActionInstant

New Repository Collaborator Added

Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.

TriggerPolling

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

Commit Event

Triggered when a new commit is pushed to a repository.

TriggerInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

ActionInstant

Connect any two apps with Notis in the middle.

Not just GitHub and Jira. Any combination from 985+ 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 Jira.