Skip to content
Notis

Track new Jira issues in Amplitude

Turn each new Jira issue into an Amplitude event, so issue intake is easier to review alongside product activity.

Trigger

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

Action

Send Events to Amplitude

Send events to amplitude using the http v2 api. this action allows you to send events to amplitude for tracking user behavior and analytics. it supports all amplitude event fields, handles proper validation, and includes comprehensive error handling.

Why this helps

New issues can disappear into a backlog before anyone can see how much work is being reported or what patterns are emerging.

  • Record issue creation in the analytics workspace you already use.
  • Reduce manual updates between Jira and product analytics.
  • Review issue intake alongside other Amplitude event data.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Amplitude once in the Notis portal.
  • 2Create an automation in the portal or tell Notis in plain language.
  • 3Ask Notis to send an Amplitude event when a Jira issue is created, using available issue details.
  • 4Pick the Jira New Issue trigger and choose where run reports should go.
  • 5Test with one real issue and review the event in Amplitude.

Questions about this workflow

Which Jira issues trigger this automation?

It runs only for issues created in the Jira project configured for the New Issue trigger.

Can I choose which Jira fields become event properties?

Describe the outcome in plain language. Notis interprets the request from available issue details; setup does not use field mapping.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Jira triggers

Amplitude actions

Recurring trigger

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

TriggerScheduled

Check Amplitude Cohort Status

Check the status of a cohort export request. this action allows you to: - poll the status of an in-progress cohort download request - determine if a cohort is ready for download

ActionInstant

Webhook trigger

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

TriggerInstant

Create Amplitude Event Category

Create a new event category in amplitude. this action allows you to: - create a new event category to organize event types - validate category name before creation key features: - creates event categories for organizing events - returns success/failure status

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Create Amplitude Event Type

Create a new event type in amplitude. this action allows you to: - define a new event type with various properties - associate the event with a category - add metadata like description, tags, and owner key features: - creates trackable events in your amplitude project - supports full event type configuration

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Delete Amplitude Event Category

Delete an event category from amplitude. this action allows you to: - delete an existing event category - remove category organization from events key features: - permanently removes event categories - returns success/failure status

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

Delete Amplitude Event Type

Delete an event type from amplitude. this action allows you to: - remove an event type from your project - mark live events as deleted - remove planned events from the tracking plan key features: - different behavior based on event status (live, planned, etc.) - returns success/failure status

ActionInstant

Request Amplitude Cohort

Get a single cohort by id and initiate download. this action allows you to: - request a specific cohort from amplitude - optionally include user properties in the response - start the asynchronous download process key features: - supports filtering by specific user properties - returns a request id used for polling status and downloading - supports eu data residency

ActionInstant

Get Amplitude Event Categories

Get event categories from amplitude. this action allows you to: - get all event categories in your project - get a specific category by name

ActionInstant

Get Amplitude Event Type

Get a specific event type from amplitude by name. this action allows you to: - retrieve detailed information about a single event type - get all properties and metadata for the event key features: - retrieves comprehensive event type details - returns metadata like category, description, and settings - supports lookup by exact event name

ActionInstant

Connect any two apps with Notis in the middle.

Jira and Amplitude, 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 Amplitude.