Hey everyone,
I’ve hit a snag with my Airtable and Jira setup. It’s driving me nuts!
My Airtable was working great with a custom Jira filter. It used to pull in all 200+ issues no problem. But now? It’s only grabbing 100 of them. This happened out of the blue today.
It’s causing a real mess. My other bases are acting up, custom filters are broken, and some of my automations aren’t running right. It’s like Airtable suddenly put a cap on things or the sync got messed up somehow.
Has this happened to anyone else? Is there some limit I don’t know about? Or maybe a quick way to fix this?
I’d really appreciate any help or ideas. This is throwing a wrench in my whole workflow!
hey swimmin shark, i ran into this too. super annoying! check ur jira api settings, they might be limiting results. also, try breakin up ur sync into smaller chunks. like do separate syncs for different project or issue types. helped me get around the limit. good luck!
I encountered a similar issue recently. It’s likely related to Jira’s API pagination, as others have mentioned. One solution that worked for me was implementing a custom integration using Zapier or Make (formerly Integromat). These platforms allow you to set up multi-step workflows that can handle pagination, effectively bypassing the 100-item limit.
If you’re not keen on using third-party tools, another approach is to modify your Jira JQL query to create multiple, more specific filters. For instance, you could split your issues by priority or status, then set up separate syncs in Airtable for each. This method requires more setup but can be effective for larger datasets.
Remember to check your Airtable sync settings as well. Sometimes, adjusting the sync frequency or manually triggering a sync can resolve unexpected limitations.
I’ve come across this problem before. In my experience, the issue is often caused by Jira’s API pagination, which limits results to 100 items per page by default. You might first double-check your Jira filter settings to ensure they aren’t filtering out additional results unexpectedly. Next, try recreating the Airtable sync and adjust the maximum record limit if possible. If that doesn’t solve the issue, consider refining your filter criteria to break your sync into smaller parts or even exploring custom API integrations to manage pagination more effectively. This approach helped me resolve similar workflow disruptions.