This article covers how to make edits to Jira issues using the Update issue and Update issue with list buttons included in the Jira and Jira Data Center Packs. Make sure you've installed and connected the Pack before getting started.
📣 With the launch of two-way sync for Jira Issues tables, you may no longer need to use the Update issue buttons. Check out this article to learn about using two-way sync to easily update your Jira issues right from Coda.
Within this article you'll find...
Use buttons to update issues
The Update issue and Update issue with list buttons let you edit multiple fields in a Jira issue in one click.
If you’re looking to update a single issue or update the same fields across a number of issues (e.g. update all issues’ summary and priority in a table), use Update Issue
. It takes pairs of fields and values; representing the new value of the given field. In the below example, we use the formula to update the Summary field to have a new title.
You'll note that rather than selecting an object, we typed in the name of the field as text rather than selecting a column from the table. The button will fail unless you type in the field name as text.
For custom fields, you will need to designate the field in the form customfield_[id]
where ID is the ID number for the custom field from Jira. This can be found using the steps in this article.
Use Update issues with list if you’re updating a set of fields that may change by button press, e.g. you want to only push specific fields that have changes. This is a more advanced function and can be used to only push select edits to the data and thus ensure you don’t overwrite or corrupt other data in Jira. To use it, create a comma-separated list of fields and values (or, use the List()
formula!). Here's an example:
Update assignee and Update priority buttons function similarly, albeit only for those fields. Again, you will need to input the values as text.
Supported Jira fields for edits
The below table reflect which standard fields from Jira are supported by Coda.
Read refers to the ability to pull in the associated field from Jira.
Write refers to the ability to push edits from Coda to Jira.
Field | Read | Write | Notes |
Assignee | Yes | Yes |
|
Attachments | No | No |
|
Changelog | Yes | N/A |
|
Comments | Partial | No |
|
Components | Yes | Partial | Editable via UpdateIssue action, but not two-way sync yet |
Created | Yes | N/A |
|
Description | Yes | Yes | Rich text isn’t always perfectly translated |
Due date | Yes | Yes |
|
Environment | Yes | Yes |
|
Epic link | Yes | Yes |
|
ID | Yes | N/A |
|
Issue key | Yes | N/A |
|
Issue type | Yes | No |
|
Issue URL | Yes | N/A |
|
Labels | Yes | Yes |
|
Linked issues | Yes | No |
|
Parent | Yes | Yes |
|
Priority | Yes | Yes |
|
Project | Yes | No |
|
Reporter | Yes | N/A |
|
Resolution | Yes | N/A |
|
Sprint | Yes | No |
|
Status | Yes | Partial | Status can be edited from Coda using two-way sync, but cannot be edited using buttons. |
Subtasks | Yes | Partial | These can be edited from Coda by editing the Parent field of the subtask. |
Summary | Yes | Yes |
|
Time tracking | Partial | No |
|
Updated | Yes | N/A |
|
The below tables shows which custom field types from Jira are supported in Coda.
Read refers to the ability to pull in the associated field from Jira.
Write refers to the ability to push edits from Coda to Jira.
Field type | Read | Write | Notes |
Paragraph | Yes | Yes | Rich text isn’t always perfectly translated |
Checkbox | Yes | Yes |
|
Radio buttons | Yes | Yes |
|
Select list (single choice) | Yes | Yes |
|
Select list (multiple choice) | Yes | Yes |
|
Select list (cascading) | Yes | Yes |
|
FAQs
Is there an easier way to update Jira issues from Coda?
Is there an easier way to update Jira issues from Coda?
Yes! In most cases, we recommend setting up an Issues table and enabling two-way sync to easily push edits from Coda back to Jira. You can read all about it here.
Can I create new Jira issues from Coda?
Can I create new Jira issues from Coda?
Yes, you can use the Create issue button to do so. Read more on this here.