This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
What is different from the original Jira Connector and the Jira Iterative Macro Connector?
Jira Iterative Macro Connector
Single API Call
Multiple (Iteartive) API Calling
Subject to server data limits
Will iterate beyond Server limits
Macro Dialogue Interface
Text Based Interface (file)
Why the need for Iterations?
We use Jira for Digital Manage for Daily Improvement (MDI) boards and Scrum boards, and the limitations of Canned Dashboards and complexity of EasyBI called for a need to extract all the data on a board and pull it into Tableau.
Due to Jira server limitations from local site admins, I was only able to pull 100 records from a given Jira Project at a time. Having Jira projects that contained thousands of records, I had a need to iterate beyond the server limitations. The iterations verify max records and iterate on a single API call until the max records for a project are received.
What input do I need to use the Macro?
The table below (also attached) outlines the following:
First Row depicts the header row
Second Row depicts the actual information you need to supply
Third Row depicts an explanation of the information you need to supply