Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers. Get Fabric certified for FREE! Learn more
Hi everyone!
I was running the JIRA content pack (https://powerbi.microsoft.com/en-us/blog/explore-your-jira-data-with-power-bi/) without any problems until today. But now I'm facing a issue that I cannot fix.
The problem is, suddenly the template started to limit the rows that are loaded from REST API. I didn't changed anything before this and I also checked if my JIRA user had some permission edition. Anybody knows what could be happening?
Thank you very much!
Hello @pollyog
I’d like to propose and alternative solution for you, you might want to try out our app - Power BI Connector for Jira: https://marketplace.atlassian.com/apps/1221150/power-bi-connector-for-jira?hosting=cloud&tab=overvie... it's available for Jira Cloud / Server / Data Center.
We have a handy User/Admin Guide https://aserve.atlassian.net/wiki/spaces/PBCFJC/overview and fast/responsive support team at support@alpha-serve.com. Please let us know if you need any assistance.
Cheers!
Anton
===
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
So, based on the last update from JIRA team:
The problem is not considered as a bug and they recommend to use pagination. The problem is, if you are using the JIRA content pack, it is already using pagination (look for GenerateByPages function), but it stopped to work after this update.
Anyone could find a way to "fix" it?
Thanks!
Hi all,
I have reported this issue on Power BI side, will update here once I get any information.
Best Regards,
Qiuyun Yu
I found that if you edit the data source in the advanced editor (using Power BI Desktop)
the second line which you can change to 100. Now that JIRA has restricted to 100 rows you can just loop on the 100 each time instead. For those that don't know.. the value 100 is referring to the pagesize that it gets when it loops through the data
let
Source = FetchPages("", 100),
Hi,
Can you explain or link to how you would do this?
Thanks!
To get PowerBi desktop to open Jira issues download and open the pbix file here
Click the data view in the left pane
Click the edit queries button and select edit queries
In the right pane you'll see a list of steps taken
Click on the top one that says Source
Change the value that appears in the formula bar to
= FetchPages("", 100)
I hope someone updates the Mircrosoft PowerBI service so that it starts working again soon as the desktop version requires manual refresh if you're publishing to the service.
Team,
Has anyone gotten this to work again using the on premise version of JIRA?
I am using a copy of the content pack that was denoted in the comments here to work with on premise, and for the life of me cannot get it to return all JIRA issues for a project.
https://powerbi.microsoft.com/en-us/blog/explore-your-jira-data-with-power-bi/
We are on JIRA version 7.10.00
I do have it fetching rows however similar to the title of this thread, it only pulls the top 50.
Thanks in advance for any help!!
Brian
Hi, thanks for the info - but I can't seem to get this working. In what area are you entering the formula?
Thanks,
Dave,
@davidbyrne1 in the advanced editor of the get data page.
Hi, thanks for the info - but I can't seem to get this working. In what area are you entering the formula?
Thanks,
Dave,
Hi all,
We got response from PG team below:
We will need to change the content pack design to accommodate for this change and we haven’t been able to get to that work item yet due to other high priority item.
Best Regards,
Qiuyun Yu
**bleep**! So think we will have to wait for a feedback from them.
Seems to be a global problem 😞
Probably some update on JIRA API...
Anyone had already fixed this?!?!
Trying to see if JIRA has made any annoucements atm, seeing as we are paying JIRA a hefty monthly fee I will try and contact them directly to see whats up. I'll report back here.
Thank you BeeEyeNoob, I'll inform here if I get some new about this.
Same issue here - my GetIssues table is now around 100 rows when it was near 47,000 just two days ago.
Same issue for the last couple of days now.
User | Count |
---|---|
101 | |
69 | |
58 | |
47 | |
47 |