Skip to content
Jira Pack guide
  • Pages
    • Jira Pack guide
    • Connect Coda and Jira
      • Sync & doc performance tips
    • Bring Jira issues into Coda
      • Add tables with Jira issues
      • Sample reports & dashboard views
    • icon picker
      Edit issues in Coda
    • Create Jira issues in Coda
    • Example docs
    • Additional resources
      • How to log into Jira using Python and the Coda Jira Pack [2024]
      • How to use story points in Jira and reporting with Coda's Jira Pack [2024]

Edit issues in Coda

Make stand-ups and triage meetings more productive by directly editing your issues in Coda and pushing the changes back the Jira.
The two-sync feature of the Jira Issues tables allows editors of the doc to directly edit the properties of an issue, such as it’s Summary, Status, Priority, and Assignee, and then push those edits back to Jira.

Enabling two-way sync

Once you’ve completed the steps outlined in , follow the instructions below to enable two-way sync.
In the Issues table, click on Options in the header and then Jira Issues in the side panel.
Under the heading Two-way Sync toggle the setting to On.
Click the button +Add a private account to setup your personal account that will be used to make edits. Follow the steps to select an existing account you’ve connected or setup a new one. ​Note: Each collaborator in your doc that wants to edit Jira issues will need to connect their own private account.

Using two-way sync

To use two way sync, simply start by editing the rows and columns in the table just like you would any other Coda table. Certain columns may not be editable, as not all fields in Jira can be changed by the user.
Cells that have been changed, but not yet pushed back to Jira, will be annotated with a blue tick in the corner.
Screenshot 2023-09-26 at 3.15.08 PM.png
To send your changes to Jira push the Send edits button located in the header of the table.
 
Want to print your doc?
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.