Skip to content
Notis

Add current BART context to Jira tickets

When a ticket could be affected by BART service, send its issue key and route to Notis to check the latest information and refresh the ticket context.

Trigger

Webhook received

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

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

A Jira ticket can lack the travel details needed to make a timely decision, especially when service conditions change after it is opened.

  • Keep transit context with the issue it affects
  • Refresh existing work without starting a separate tracking thread
  • Use current information returned by Bart

Setup

Build it in a few focused steps.

  • 1Connect Bart and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it.
  • 3Tell Notis to use the request's Jira issue and BART route to check service information and update the ticket with relevant context.
  • 4Pick the webhook trigger and choose where run reports should go.
  • 5Test with one real issue and route, then review the change.

Questions about this workflow

What should the webhook request contain?

Include the Jira issue key, the BART route or station, and any work context that helps Notis decide which returned details matter.

Will the issue be updated if there is no relevant information?

The instruction can ask Notis to leave the issue unchanged unless the Bart check returns useful context.

Can this start from a Jira event?

No Jira trigger is part of this source-to-target package. The workflow starts with a Notis webhook request.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

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

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