Hi Gyanendra,
This is a common pain point with the standard Jira API connection in Power BI, since the built-in connector doesn't support incremental loading out of the box, it just pulls the full dataset every time.
A couple of things that might help:
1. If you're using the JQL/REST API query directly in Power Query, you can filter by the "updated" field (something like updated >= "-1d" in your JQL) so you only pull issues changed recently, then merge that with your existing dataset instead of reloading everything. It takes a bit of Power Query setup (append queries + removing duplicates by issue key) but it works.
2. If you don't want to build that manually, there's a dedicated marketplace connector (Power BI Connector for Jira, sometimes offered by Tempo/AlphaServe) that has proper incremental refresh support built in, so it only pulls updated records automatically.
Native Jira + Power BI's own incremental refresh feature struggles here because incremental refresh in Power BI expects a reliable, immutable date column to partition on, and Jira's "updated" field can shift due to automations or bulk changes, so you may need to test carefully whichever route you pick.
Hope this gives you a starting point!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.