Automatically Assign Jira Tickets to PR Authors
You open a pull request. Notis automatically assigns the matching Jira ticket to you, so ownership is always clear.
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.
Action
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Why this helps
Pull requests and Jira tickets get assigned to different people. You can't tell who owns a piece of work at a glance. Accountability is scattered, and followups go to the wrong person.
- Keep Jira assignment in sync with code ownership
- Clarify accountability across tools
- Reduce manual ticket assignment
- Ensure work ownership is always clear
Setup
Build it in a few focused steps.
- 1Connect GitHub and Jira to Notis.
- 2Tell Notis: 'When a new pull request is opened, assign the matching Jira ticket to the PR author.'
- 3Set trigger to 'New Pull Request Created' and action to 'Assign Issue'.
- 4Notis will look up the PR author's Jira account and assign accordingly.
- 5Test by creating a pull request and verifying the Jira ticket gets assigned to you.
Questions about this workflow
What if the PR author doesn't have a Jira account?
The automation will skip or fail gracefully. Ensure all GitHub users have Jira access first.
How does Notis match the PR author to a Jira user?
By email address or username. Configure in your prompt if mappings differ between GitHub and Jira.
Can I add them as a watcher instead of assigning?
Yes—modify the action to 'Add Watcher to Issue' instead of 'Assign Issue'.
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 triggers
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.
Add Attachment
Uploads and attaches a file to a jira issue.
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.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
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.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
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.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
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.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
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.
Link Issues
Links two jira issues using a specified link type with optional comment.
Commit Event
Triggered when a new commit is pushed to a repository.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Not just GitHub and Jira. 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 Jira.