We have a table created using a JIRA query that is bringing in Jira data from 2 specific Jira project boards, along with a specific set of statuses and other criteria.
At some point it started syncing in data from our entire Jira database, so instead of a few hundred results, it’s pulling in several thousand.
I tried updating the filter a few different ways to only bring in tickets from a single project or reduced the number of additional qualifiers, but nothing seems to work, and usually the whole page ends up crashing/freezing because there so much data being processed.
I’m wondering if the table somehow became corrupt? Hoping there is a way to fix it, or is my best bet to delete the table completely and start from scratch?
@Chris_Branaman
In the pack settings
, you can nominate which project/s to sync from.
There’s a Jira Pack Guide here from Coda which will run you through how to do certain things (incl. troubleshooting sync issues etc)
Hope this helps!
Mel
Thank you for the response, I’ll check out the resources. But for clarification, the original JQL query worked just fine and pulled in exactly what we wanted from a couple of different project boards. Then for an unknown reason, it seems that tickets from our entire Jira instance were getting pulled in, instead of only the ones defined by the query.
This is coda side. It’s gatekeeping/limiting what comes into coda.
Your JQL query deals with what’s happening on Jira side
Check your Jira pack settings. Maybe it got changed and hence why everything is coming in now
Still curious though how the Jira sync (query) would work just fine in one table but not in another?
Also we do want to pull from multiple boards (not just a single Project) and then filter the results through the sync query.
In the Jira pack settings, there’s a + Add criteria button underneath account.
Here you can filter what to bring into coda incl. project name, jql query , assignee name, label etc
Right and we are using a JQL query. I’m actually using that same query on in two different Docs. One of them is working as intended, the other is not. All other settings between the two docs are identical.
In that case probs best to contact coda support. they can troubleshoot and determine if its a bug
2 Likes
