Spot issue dependencies before they become blockers
Create a Coda dependency review page alongside each new issue, with a place to record blockers and needed coordination.
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
Create a page
Create a new page in a doc. note that creating a page requires you to be a doc maker in the applicable workspace.
Why this helps
Dependencies often surface late when no one has a shared place to write down what the issue relies on.
- Make dependencies easier to identify and discuss.
- Keep blocker context visible alongside issue details.
- Provide a shared place for coordination follow-up.
Setup
Build it in a few focused steps.
- 1Connect Jira and Coda once in the Notis portal.
- 2Create an automation from Automations, New Automation, and give it a name.
- 3Tell Notis to create a Coda dependency review page for each new Jira issue with available details and sections for blockers and coordination needs.
- 4Pick the Jira New Issue trigger and choose where run reports should go.
- 5Test with one real issue and check that the page distinguishes known dependencies from questions to investigate.
Questions about this workflow
Can Notis infer dependencies that are not in Jira?
No. Use information returned by Jira or Coda, or have the page provide a place for people to identify dependencies.
Does the trigger watch all Jira projects?
It watches the project you configure for the New Issue trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Coda. A trigger fires from one place; an action lands in another.
Jira triggers
Coda actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add a category for pack
Add a publishing category for a given pack.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add a maker for pack
Set a maker for a given pack. used to display makers for a pack in the corresponding packs page.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Add a permission for pack
Create or modify user, workspace, or global permissions for a given pack.
New Project
Triggered when a new project is added in Jira
Add custom domain
Add a custom domain to a published doc.
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.
Add permission
Adds a new permission to the doc.
Begin content export
Initiate an export of content for the given page.
Content export status
Check the status of a page content export
Copy Document
Creates a copy of an existing coda document. this action allows you to duplicate a document while optionally specifying a new title and location for the copied document.
Connect any two apps with Notis in the middle.
Jira and Coda, 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 Coda.