Edit a Jira issue when a Notion page is updated
Your Notion page keeps evolving as you learn more, but the Jira ticket often freezes at whatever it said on day one. Notis watches for content edits on the page and updates the linked Jira issue to match, so the ticket your team reads always reflects the latest thinking instead of a stale first draft.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
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
You keep refining the Notion page, but the Jira issue stays stuck on old details, so the team builds from outdated instructions.
- The Jira issue reflects your latest Notion edits instead of a frozen first version
- Your team builds from current instructions, not yesterday's draft
- You update one place and let the other catch up on its own
Setup
Build it in a few focused steps.
- 1Connect Notion and Jira to Notis a single time from the portal.
- 2Open the portal link Notis provides and start a New Automation.
- 3Write the instruction plainly, for example: When I update the content of a linked Notion page, update the matching Jira issue.
- 4Choose the Page Content Updated trigger and set your channel for run reports.
- 5Edit one page and confirm the Jira issue reflects the change.
Questions about this workflow
Does Notion batch content edits?
Notion aggregates content edits within a short window, so a burst of quick edits usually results in a single tidy update to Jira.
Can I scope it to one page or database?
Yes. Name the specific page or the data source in your instruction and Notis limits the automation to it.
Which Jira fields get updated?
Notis updates the fields your instruction implies, such as the description or summary, based on what changed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Jira. A trigger fires from one place; an action lands in another.
Notion triggers
Jira actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Add Attachment
Uploads and attaches a file to a jira issue.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
New Page
Triggers when a new page is added to a Notion database.
Link Issues
Links two jira issues using a specified link type with optional comment.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Not just Notion and Jira. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Jira.