Skip to content
Notis

Keep Jira location details current with scheduled checks

Have Notis revisit location details on a schedule and update the relevant Jira issues with validation findings, so stale information is easier to spot.

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

Location details can become stale while tickets stay open, and teams may not notice until they cause delays.

  • Bring scheduled validation findings back to the open work.
  • Make questionable details easier to notice in context.
  • Reduce manual ticket review for location changes.

Setup

Build it in a few focused steps.

  • 1Connect Big data cloud and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it for the Jira location review.
  • 3Describe in one instruction which supplied Jira issues and location details to validate and how to update each issue with the result.
  • 4Pick a recurring schedule trigger and choose where run reports should go.
  • 5Test with one real issue and confirm the update is useful.

Questions about this workflow

How does Notis know which Jira issues to check?

Supply the selected issues or describe an accessible source for the issue references and location details in the instruction.

What does the update contain?

The update can summarize validation findings and identify details that remain uncertain for human review.

Can it fix incorrect location data automatically?

Only use automatic corrections when the right value is supported by the lookup result. Instruct Notis to flag uncertain cases for review.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Big data cloud 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.

Big data cloud 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.