How to automatically generate Jira issues whenever a Coda row is modified

In this how-to guide

How to automatically generate Jira issues whenever a Coda row is modified
1. Set the Coda trigger as “Row changed”
2. Add the “Create issue” step in Jira
3. Activate your playbook
Learn more about integrating with Jira and Coda
Related blog posts
More how-to guides featuring Jira and Coda

Integrationsarrow_forwardCoda Integrationsarrow_forwardCoda + Jira Integrationsarrow_forward

Relay.app is an automation tool that lets you automate actions across Jira, Coda, and many other apps. In this guide, we'll show you how to automatically run the “create issue” action in Jira for each row changed in Coda using Relay.app.

Try it in Relay.app

Coda > Jira

Trigger

Last triggered

Row changed

Create issue

Set the Coda trigger as “Row changed”

Add the Coda trigger to initiate your playbook's actions when a row is changed.

To do this, click "Add trigger" in your playbook. Select the "Row changed" trigger option from the dropdown menu under Coda. It will enable your playbook to automatically identify newly changed rows and trigger necessary actions.

If you still need to connect your Coda account to Relay.app, a prompt will guide you through the connection process.

Add the “Create issue” step in Jira

Integrate the Jira automation into your playbook to ensure the prompt creation of Jira issues whenever a Coda row is changed.

Click the "Add step" button, then locate the “Create issue” automation for Jira and input the mandatory and relevant details.

If your Jira account still needs to be connected to Relay.app, you will be prompted to complete that connection. Make sure to allow the necessary permissions for Relay.app to sync with your Jira account.

Activate your playbook

Activating your playbook is the last step in the process. Once you turn it on, it will automatically generate Jira issues whenever a Coda row is changed without requiring manual intervention.

To activate your playbook, click the toggle button at the header. Before activating, we recommend performing a test run of your playbook to ensure all the steps work seamlessly together.