Jira Error for specific project

[datanerd]

I am working to connect Jira to Power BI.  The specific project url for our company was entered into the url section when connecting to the Jira Service.  However I am getting the following failure.  When going to our overall coorporate jira url then it works but does not allow me to filter down to our project/team.  I have went into the report editor in order to apply a filter but the column needed for filtering to our specific project doesn't appear. 

Thanks for any insight. 

[v-yulgu-msft]

Hi @datanerd,

To connect to JIRA content pack, the required JIRA URL should be formatted as http://yoursitename.atlassian.net. 

Here is a similar thread for your reference: Import of JIRA issues is failing

Best regards,

Yuliana Gu

[datanerd]

That does allow me to sign in and get past the error.  However, the results returned is extremely limited.  I am not seeing all of our projects listed when I bring up a slicer/filter for the project.  We have 50 or so projects.  This is Jira Cloud as well.  

[v-yulgu-msft]

Hi @datanerd,

However, the results returned is extremely limited.  I am not seeing all of our projects listed when I bring up a slicer/filter for the project.  We have 50 or so projects.  This is Jira Cloud as well.  

---

For the data limitation problem, it is related to the JIRA API. You should consult with the API developer whether the API can return all records.

Regards,

Yuliana Gu

[datanerd]

This is Jira Cloud so it is hosted by Atlassian.  The API is default of 50 records per page with a limit of 100.  I have built a customer API client to pull all the pages down from Jira.  However, that is a .net application not something that I can add onto PowerBI.  Without this working for the solution template, it renders the template useless for Jira Cloud customers and should probably be noted in the description.  

Thanks,

Dan

[datanerd]

Are there any further thoughts on support for Jira Cloud? Like I said it can log in but does not page through the results to recieve all the issues from the Jira API apparently.