Skip to content
Jira Pack guide
Jira Pack guide
Connect Coda to Jira
Bring Jira Issues to Coda
Create Jira Issues in Coda
Example docs
More
Share
Explore

icon picker
Create Jira Issues in Coda

Learn how to create new issues in Coda and push them to JIRA using this step-by-step guide.
First, create a new base table with a minimum of 4 columns.
⁠
This link can't be embedded.
⁠
⁠
As recommended in the above video, you can start with a simple table containing 4 columns:
Summary (Text type, this will map to the Issue Title in JIRA)
Description (Text type, this will map to the Issue Description in JIRA)
Issue Type (Recommend making this a Select List column with the specific issue types available in your Jira account)
Submit or Create button column (Button type. See the below simple table. View the button options to see the set-up)

You can only populate the following 3 fields in Jira using Coda’s Pack for JIRA:
1. Summary (Issue Name)
2. Description
3. Issue Type (Bug, Task, etc)*
* It is not possible to create an Epic issue type at this time.
Search
Summary
Description
Issue Type
Submit Bug
1
This is the title for my new JIRA bug
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
Bug
Submit this row to Jira
There are no rows in this table
⁠
Here is the JIRA created based on the information above:
⁠
image.png
⁠
⁠
Next, optimize your table. Make your table more user-friendly with these quick tips.
Tip #1: Add columns to your table to track which issues have been submitted.
Adding a column to track submitted information allows you to filter the table and display a confirmation to others when an issue is created. You can also disable the button once the issue has been submitted in order to eliminate potential duplicate issues.
Search
Summary
Issue Type
Update Submitted Info in this table
Submitted to JIRA?
Submitted Date:
1
This is the title for my new JIRA bug
Bug
Submit Issue + Update Other Columns
There are no rows in this table
⁠

The button options include the formula RunActions, which enables the button to take multiple actions at the same time. In this case, the Run Actions formula will perform the following three actions: (1) submit the issue to JIRA (2) update the submitted to JIRA column in this table, and (3) update the submitted date column in this table.
⁠
image.png
⁠
⁠
Tip #2: Bring the Jira Issue Key back to Coda.
Once the issue is created, Jira assigns the issue a key (ex: DELO-234). As part of the same button action, you can bring that Key back to your table in Coda.
Search
Summary
Description
Issue Type
Submit & Receive Jira Key Back
Results (Hide)
New Jira Key
1
This is the title for my new JIRA bug
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
Bug
Submit this row to Jira
13789
DELO-24
There are no rows in this table
⁠

In the example above, we took two steps to make this happen:
Add twp new columns to your table. (In our example below, the results and new Jira Key columns.)
In the example below, the results column receives a package of information back from Jira.
Since the data that’s returned isn’t in a useful format, we create a second column New Jira Key to re-format the information into the useful information. (For those that want the more technical details, We are parsing JSON sent back to Coda from Jira to pull out the Jira Key.)
Review the review Jira Key formula to parse the Results column. Use #/Key to bring back the Jira Key
⁠
image.png
⁠
⁠
You can hide the results column from view.
Update the button options to send the results to your new column.
⁠
image.png
⁠
⁠
Tip #3: Use the concatenate formula to include more information into your issue title or description.
The summary and description attributes can include additional information or help with correctly labeling your JIRA issues with the right format. Review the button options to see the formula for the summary field.
Search
Summary
Description
Issue Type
Workstream
Concatenate issue name
1
This is the title for my new JIRA bug
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
Bug
Lightening
Submit Workstream + Summary
There are no rows in this table
⁠
The issue title can now be formatted to include important information and pull data from multiple Coda columns. Here is an example of the created JIRA title:
⁠
image.png
⁠
⁠

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.