Automatically Assign Issues to Sprints Based on Labels
A GitHub issue gets labeled 'ready-for-sprint'. Notis instantly moves the matching Jira ticket into this sprint's board.
Trigger
GitHub Issue Labels Changed
Triggers when the labels on a specific GitHub issue change. Fires whenever a label is added to, removed from, or has its metadata (color, description) modified on the monitored issue. The payload includes: - ``current_labels`` -- the full set of labels currently on the issue - ``added_labels`` -- labels that were newly added - ``removed_label_names`` -- names of labels that were removed - ``changed_label_names`` -- labels whose metadata changed without being added or removed
Action
Move Issues to Sprint
Moves one or more jira issues to a specified active sprint.
Why this helps
Issues pile up in GitHub with status labels, but getting them into Jira sprints requires manual updates. Sprint planning meetings involve copying work manually from GitHub, creating duplicates and missed items. Label changes don't trigger any updates in Jira.
- Automate sprint planning based on GitHub labels
- Eliminate manual ticket movement
- Ensure labeled work lands in sprints immediately
- Sync team priorities between tools
Setup
Build it in a few focused steps.
- 1Connect GitHub and Jira to Notis.
- 2Tell Notis: 'When a GitHub issue is labeled with a sprint-ready label, add it to the active Jira sprint.'
- 3Set trigger to 'GitHub Issue Labels Changed' and action to 'Move Issues to Sprint'.
- 4Define which labels trigger sprint assignment (e.g., 'ready-for-sprint', 'priority-high').
- 5Test by labeling a GitHub issue and verifying the Jira ticket moves to the active sprint.
Questions about this workflow
How does Notis know which sprint to use?
You specify the sprint name or configure Notis to use the current/active sprint.
What if there's no matching Jira ticket?
Use your prompt to create one first, then move it to the sprint.
Can I use multiple labels for different sprints?
Yes—set up separate automations for each label-to-sprint mapping.
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.