Skip to content
Notis

Keep Jira website issues aligned with current page evidence

When a live page changes, bring the ticket back up to date so the next person does not start from stale information.

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

Jira issues about a live page can lose value when the page changes but the ticket stays untouched.

  • Revisit Jira issues that reference web pages.
  • Update relevant issue details when page evidence has changed.
  • Reduce investigation time caused by stale ticket context.

Setup

Build it in a few focused steps.

  • 1Connect Agenty and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name the recheck.
  • 3In one instruction, define which Jira issues to review and how Notis should update them when Agenty finds a relevant page change.
  • 4Choose a recurring schedule and select where run reports should go.
  • 5Test with one real Jira issue that references a live page.

Questions about this workflow

How does Notis find the relevant Jira issues?

Describe the issue search criteria in the instruction, such as a project or JQL query. The workflow uses Jira search and issue update actions as needed.

Does Agenty update Jira directly?

No. Agenty checks the web page; Notis uses Jira to update the issue when the result warrants it.

What if the issue does not include a page URL?

The instruction needs a way to identify the page, such as a URL in the issue details. If that information is missing, Notis cannot recheck that issue reliably.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

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

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