Skip to content
Notis

Keep Jira work informed by new public research

Have Notis revisit a topic on a schedule and add genuinely useful new context to the Jira issue already tracking it.

Trigger

Recurring schedule

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

Action

Edit Issue

Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.

Why this helps

Issues lose context as public information changes, and manually checking every active topic is easy to put off.

  • Bring relevant new public information back to the issue tracking the work.
  • Cut repetitive searching across active topics.
  • Keep updates tied to existing work instead of scattering them across notes.

Setup

Build it in a few focused steps.

  • 1Connect Ceramic and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, or tell Notis from any channel.
  • 3Describe which issue or topic to revisit and what counts as meaningful new context.
  • 4Pick a recurring schedule as the trigger and choose where run reports should go.
  • 5Test with one real issue and check that the update adds useful context.

Questions about this workflow

Can Notis find an issue automatically?

Notis can analyze available information, but tell it how to identify the relevant issue, such as providing its key or a search rule in your instruction.

Will it update an issue if the search finds nothing new?

Instruct Notis to leave the issue unchanged when the search does not provide meaningful new information.

Can Ceramic provide private or internal Jira history?

Ceramic Search returns public web content. Jira issue details come from Jira, and any missing history or baseline should be supplied or treated as unknown.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Ceramic 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.

Ceramic 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.