Skip to end of banner
Go to start of banner

Best practices to be followed for Power BI Jira Connector refreshes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Overview

This article explains best practices for Power BI Jira Connector to avoid performance (loading time) issues.

Best Practice

  • Avoid any concurrent refreshes, i.e., Avoid refreshing two or more connectors simultaneously.

  • For refreshing the “History” fields, leverage the filter option to further filter history data.

    As an example below, History fields are filtered on “Flagged“ and “status“ attributes
  • If there is a lot of data, or if it takes a long time to refresh, you can split the refresh into multiple extracts based on the category or data.

  • Remove unused connector fields from the selection.

  • Limit to the minimal fieldset while choosing the performance-sensitive fields like “Sprint Metrics”, “Remote Links”, etc.

  • Limit to the minimal fieldset while choosing heavy data categories like “History”, “Work logs,” etc.


  • These are basic recommendations and may have some other factors as well. 
  • No labels