Organize release follow-up in an active Jira sprint
After a release review, gather the selected Jira follow-ups into the active sprint your team has chosen.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Move Issues to Sprint
Moves one or more jira issues to a specified active sprint.
Why this helps
Release follow-up issues remain spread across the backlog, making the next work session harder to organize.
- Collect selected release work in one active sprint.
- Use a Jira search and sprint reference supplied by your team.
- Reduce manual issue-by-issue sprint updates.
Setup
Build it in a few focused steps.
- 1Connect Jira once in Notis and define how release follow-up issues are identified.
- 2Create an automation and specify the active sprint to receive the selected issues.
- 3Choose a recurring schedule and where run reports should go.
- 4Test with one real issue and confirm the target sprint is active and correct.
- 5Review the moved issues and the run report.
Questions about this workflow
Does this create a sprint?
No. It moves issues into a specified active sprint. Create or identify that sprint separately before the run.
How are issues selected?
Provide a JQL query or other criteria grounded in fields your project uses. The workflow should not assume an undocumented release label.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Buildkite to Jira. A trigger fires from one place; an action lands in another.
Buildkite triggers
Jira actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Attachment
Uploads and attaches a file to a jira issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Buildkite and Jira, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Jira.