Skip to content
Notis

Move resolved processing tickets to the next state

Clear completed processing work from the active queue when supplied results confirm the issue is resolved and Jira offers the intended transition.

Trigger

Recurring schedule

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

Action

Transition Issue

Transitions a jira issue to a different workflow state, with support for transition name lookup and user assignment by email.

Why this helps

Resolved processing tickets can remain in active states until someone remembers to update them.

  • Keep issue states aligned with confirmed results.
  • Reduce manual cleanup of completed work.
  • Help active queues reflect current work.

Setup

Build it in a few focused steps.

  • 1Connect 0CodeKit and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name.
  • 3In one instruction, tell Notis to match supplied resolved 0CodeKit results to Jira issues and transition only eligible issues to the named workflow state.
  • 4Pick a recurring schedule and choose where run reports should go.
  • 5Test with one real resolved issue and confirm its available transition before using the schedule.

Questions about this workflow

Does this close every issue in the project?

No. The instruction should limit changes to issues matched to supplied resolved results, and Jira must offer the requested transition.

What if an issue is not actually resolved?

Only include reliable resolution results in the data supplied for the run. Review a test run before enabling the recurring schedule.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

0CodeKit triggers

Jira actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Add Comment

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

ActionInstant

Add Watcher to Issue

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

ActionInstant

Assign Issue

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

ActionInstant

Bulk Create Issues

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

ActionInstant

Create Issue

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

ActionInstant

Link Issues

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

ActionInstant

Create Project

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

ActionInstant

Connect any two apps with Notis in the middle.

0CodeKit 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.