Facing some issues in connecting Jira Date & Timing ?

[Santhosh Raj]

Hi Team,

I have created a Power BI report in Desktop and Published it into Service. Also we are using Power BI Connector for Jira a Plugin in Atlassian Jira Software. and everything is working well except the Date/Time. 
For Example we are capturing a Date/Time from Jira. So once this data is imported to Service. 
the refresh is not getting correct values as expected. It takes some hours to reflect in Power BI service. 
What timing does Power BI Service generally takes to reflect the exact date in the report ?

 

We are using Abu Dhabi timing +4:00 timing in refresh schedule. So could you help me if there is something like that. 
we are working as per IST +5.30 Does this things have to do with this timing ?

[David Nickell]

I have tons of data flowing into power bi from the APIs so I don't know what manipulation the plugin may do...

but in my case when I am processing any record, I have to TRANSFORM the date fields in power query in 2 steps (1 to DateTimeTimezone.  2. Date/time). and a 3rd time to get to date.

Hope this helps

[Marc - Devoteam]

Hi @David Nickell 

I'm not a PowerBI guy, but I mentioned something the same. This based on the nature of the question.

I know the app described and it just gets data from Jira, based on a created connector and stores this temporarily (hashed) and then in PowerBI you can fetch this info and use it in the way you see fit.

Same as using the API directly.

So I think the setup of the report in PowerBI has problems, not the data thats imported.

[David Nickell]

Sorry for any confusion -- the steps I shared are in power bi once the data has been pulled.  Essentially through the API or connector, you get a table of data that may not be formatted to your taste (as in the case of the date fields).   You use Power Query (in Power BI) to format those fields before adding them to a Visualization.

in this zoomed out from within Power BI -- Box 1 shows where I get the data.  Box 2 shows where I applied the reformatting.

[Marc - Devoteam]

Hi @David Nickell 

That's what I meant as well.

I think @Santhosh Raj just has issues in the report they build, not in getting the raw data from Jira.

[David Nickell]

I don't follow the issue completely -- but run this rest call in your browser (your URL and key of course)

https://splitdimedata.atlassian.net/rest/api/2/issue/CSP1-11

Then look at the JSON and see if one date looks different than the rest.

When you get your Power BI Connector feed, you should be able to see if what may be different in their date handling.

Good luck

 

[Santhosh Raj]

I would like to know that, if we can able to save alone the date in Resolved and not the time, But that is what getting confused. 
For created, Updated & Resolved, it shows date with time. 
and We have updated the Jira timing to +4:00 and in Power BI it should have fetched the data from Jira, But it shows some  lack of it. 
For example:
If an ticket is resolved in 10/12/2024 09:00AM (+4:00UTC)
An refresh happens in Power in next 1 hour is not fetching the data, the date is little weird when compared to both Jira and Power BI and confused which one to change @Marc - Devoteam @David Nickell 

[Marc - Devoteam]

Hi @Santhosh Raj 

Getting information from the API doesn't relate to the time setting in the system.

The API uses UTC as the default, this is not changeable.

See also https://jira.atlassian.com/browse/MP-73 

You also see this in the screenshot from @David Nickell 

Also all fields you mention are date/time fields. In PowerBi you should transfer this as required fro your report.

[Marc - Devoteam]

Hi @Santhosh Raj 

Hi as the PowerBi service takes its time contact Microsoft.

AS you stated it takes heaps of time in PowerBI, but the data comes over as planned

Is the setup on data/time in the PowrBi report some strange calculation?

I don't see this as an App or Jira issue, but a PowerBI issue.

I f you want more details from the app used in Jira or support, contact the support department from the app in this case.

Also check their documentation on date, see How+Time+in+Status+Time+With+Assignee+tables+are+calculated