Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hello
I am using Power BI desktop to analyze some data from JIRA tool.
For this, I installed a Power BI connector on JIRA.
The dashboard refresh on Power BI desktop works very well. I published this dashboard on Power BI Services and scheduled refresh each days.
I am encountering an issue. I don't have the same result in Power BI Desktop and Power BI Services after refresh.
This issue appears on a new measure whose formula is:
Days_actual_Worklogs_Adjusted =
IF(
'Worklogs'[LOGGED_TIME] / (8 * 3600) > 0;
'Worklogs'[LOGGED_TIME] / (8 * 3600);
1 / 8 // Correspond à 1 heure de travail minimum
)It seems this formula does not work in the same way between Power BI Services and Power BI Desktop.
Could you please support me to solve this issue?
Thanks
Sébastien
Solved! Go to Solution.
Hi @Seb_Bonnet ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hi @Seb_Bonnet ,
Since the values are consistent in Power BI Desktop and Jira but differ in Power BI Service (specifically for 07/28/2025), the issue likely stems from how the data is refreshed or interpreted in the Service.
Please review the following:
LOGGED_TIME_Adjusted = 'Worklogs'[LOGGED_TIME] + TIME(2, 0, 0)
This is important as Power BI Service uses UTC, while Desktop uses your local time.
After publishing and refreshing, use “View Data” in the Service to check if the expected rows (e.g., 46800s for AMAZON LAB126 on 07/28) are present. If missing, data might be getting filtered or dropped during refresh.
Ensure the gateway is configured properly and that the Service is connecting to the same JIRA project/data scope as Desktop. Any difference in permissions or filters can lead to partial data loads.
Review any applied filters, especially on datetime columns. These may behave differently in Service if not adjusted for UTC.
Try republishing after verifying the above. Hope this helps. Please reach out for further assistance.
Thank you.
Hi,
I didn't find any way to solve this issue.
With the same formula, I have 23 days logged for a user.
After publishing and refreshing in Power BI Service, the values are different.
I checked the values on POWER BI desktop and these values are the same as in JIRA.
But in POWER BI Services, it is not correct, specially in 07/28/2025.
Do you have any idea?
Thanks
Sébastien
Hi @Seb_Bonnet ,
Thank you for reaching out to the Microsoft fabric community forum. Also thank you @Akash_Varuna for your inputs.
The difference you're seeing between Power BI Desktop and Power BI Service is likely due to timezone differences Power BI Desktop uses your local time zone, while Power BI Service runs in UTC.
To align results, check if LOGGED_TIME from JIRA is in UTC.
LOGGED_TIME_Adjusted = 'Worklogs'[LOGGED_TIME] + TIME(2, 0, 0)
Also, confirm your dataset refreshes correctly via the gateway and that both environments are loading the same data version.
I hope this will resolve your issue, if you need any further assistance, feel free to reach out.
Thankyou.
Hi @Anonymous
Thank you for your feedback.
I think the problem is not in the formula.
Indeed, Worklogs[LOGGED_TIME] corresponds to the work logged in the task in seconds. So, I don't think the Timezone as an impact on the formula.
But, to buil the table, we are using a date filter as follows
Maybe the timezone has an impact on the filter.
Could you please confirm it?
Thanks
Sébastien
Hi @Seb_Bonnet ,
Thank you for clarifying. You're correct, the formula isn't affected by the timezone, as LOGGED_TIME is stored in seconds. The difference most likely comes from the date filter used in the table.
Power BI Desktop uses your local timezone, while Power BI Service operates in UTC. If JIRA logs something late in the day (for example, 28/07/2025 23:30 local time), the Service may treat it as 29/07/2025 in UTC. So, when filtering for July 28th, this entry would show up in Desktop but not in Service.
To fix this, you can:
This should help both Desktop and Service interpret the dates the same way, making your July filter return consistent results.
I hope this provides the clarification you needed. If you have any further questions, please do not hesitate to reach out.
Thank you for being part of Fabric Community.
Hi @Seb_Bonnet ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
@Seb_Bonnet Ensure there are no time zone differences between Power BI Desktop and Power BI Services. Check that both environments are using the same data version and that Power BI Services is updated after each refresh. Review regional settings that might affect the formula's calculation. Lastly, verify the custom JIRA connector works the same way in both environments.
Thank you for your feedback.
I checked the regional ssetings and I have the same configuration on the 2 dashboards.
Regarding the time zone, could you please give me guideline to check it.
For JIRA connector, I think it works the same way in both environments.
Thanks
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
| User | Count |
|---|---|
| 11 | |
| 11 | |
| 9 | |
| 8 | |
| 8 |