Make issue handoffs easier to pick up
When a Jira issue changes, give the next person a Coda doc with the context and follow-up they need to continue.
Trigger
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.
Action
Create doc
Creates a new coda doc, optionally copying an existing doc. note that creating a doc requires you to be a doc maker in the applicable workspace (or be auto-promoted to one).
Why this helps
A changed issue can leave the next owner reconstructing context before they can take action.
- Put handoff context in one place.
- Make ownership transitions easier to follow.
- Reduce repeated explanations when work moves between people.
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 what issue changes call for a handoff doc and which available details and follow-up sections to include.
- 4Pick the Jira Updated Issue trigger and choose where run reports should go.
- 5Test with one real change and review whether the doc gives the next owner enough context.
Questions about this workflow
Can this be limited to assignee changes?
The trigger fires when an issue field changes. State the handoff condition in your instruction and use only change data available from Jira.
Are issue comments included as trigger events?
No. This trigger does not fire on comment activity.
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.