With the Jira pack, you can sync your Jira issues into a Coda table, keeping your doc up-to-date with the latest changes in Jira. However, you might not want to sync all of your Jira data into Coda. In this article, we’ll walk through some of the ways you can filter down the data that pulls into your Jira data sync.

When would I want to use these options? Why wouldn’t I want to sync in all Jira data?

Often times you don’t need to see all the things everyone at your company is working at. These sync options reflect that reality and empower you to filter down the data as you see fit. More specific examples may include:

  • I only want to see tasks assigned to me or a teammate

  • Our team only wants to see tasks associated with a project we’re working on

  • Multiple teams actually handle different parts of the same project, so we only want to see the fields that are relevant to us

Where to find the sync options

All the options discussed in this article can be found by hovering over the Jira Pack’s Issues table and clicking “options” and then the “Jira Issues” tab at the top of the menu. From here, you can click on the “Add Criteria” button which should open a dropdown menu of the different options.

Using the Project Criteria

One of the easiest ways to filter down the data that comes into your Jira Issues table is to only pull in specific projects from your Jira Workspace. You are limited to selecting one project in this dropdown but you can add another sync and select another project. The issues from the different projects will all pull into the same Issues table but you can create filtered views for the different projects. You can also set up the Pack in another doc if you can separate out the Issues and Projects into a separate doc.

An additional benefit to using the Project criteria is Coda will only bring in the fields associated with a specific Project instead of pulling in all fields associated with the Jira workspace.

Using the JQL Query Criteria

Another way to filter down the data that comes into your Jira Issues table is to use the JQL (”Jira Query Language) Query option from the “Add Criteria” button. For this option, we have a dedicated article here explaining how to obtain and insert the JQL Query into the Issues table.

Note that this option does not support the same field restricting behavior that the Project criteria do.

Using the Fields Criteria

Like the other options, the Fields Criteria limits the content pulled in. But instead of doing so by the project or attributes of issues the Fields criteria limits which fields get pulled over from Jira into Coda. This is useful for helping you “focus” your view of Jira down to the fields your team needs to see in Coda, rather than overwhelming them with all the fields that might exist in your Jira workspace.

Tip: if you ever see an error message about there being too many fields, you can use this setting to reduce the amount of fields and solve the error.

Giving Us Feedback

Have ideas for other ways to filter down data in Jira? Feel free to give that feedback in the support chat or by writing an email to support@coda.io.

Did this answer your question?