'Tis the season to be spooky! Read our new blog, How Spooky is Your City? Mapping and Predicting Scary Stuff. In it, @SusanCS provides a fun glimpse into using data to figure out the creepy quotient of where you live! And don't forget to check out our Digital Costume Thread to get yourself in the mood for a candy binge!
My organization has been using this macro for about a year. Great job with it!
Recently, JIRA has changed their API to no longer accept user name. Instead, they accept account number. Replacing my username with account number doesn't work with this macro. Is there any way to revive the macro now that the API has changed?
I'm using the macro with an email address and the Jira token (instead of the password).
The only disadvantage with this approach is that you can't filter the issues based on the user name so basically you get all the issues for the project.
All - Just as an FYI, I no longer have the time to work on further development and/or bug fixes for this project. I would encourage anyone and everyone to feel free to pick this up and submit new & improved version in the Gallery. Thanks for all of the great feedback!
Having an issues with getting a full list of issues via Alteryx.
By downloading JIRA issues via the connector I'm receiving a different number vs same API request via a browser. I figured out that API request via Ateryx is missing all the issues which have the security level in place.
Did anyone come across the problem with the security level?
We need some help to use this JIRA connector, my use case is as mentioned below.
Wants to fetch all Open Bugs by CreatedDate (here CreatedDate will be filter) and want to get all Closed Bugs by Resolveddate.
I am not sure in this connection can we able to provide condition as Createddate and can we able to download all bugs.
Please help us.
Based on my research, the JIRA Connector broke when the newest version of the JIRA API was released. The creator of the JIRA Connector posted that he is not supporting it any longer. Unfortunately this leaves the Connector as non-functioning in its current form. He did mention that he hoped that someone else would pickup the Connector, update it and increase its functionality. Most people are using the basic Download tool with the JSON Parse tool to build custom solutions for pulling data from JIRA. Sorry for not having a more positive response for you.
@bhaushedbale, I created a custom Python tool to pull Jira data for myself. Since the creator of this connector is not supporting it, I assume there is no issue if I link mine in here?
You can view the source code on GitHub and download the latest version from this releases page (look for JiraPy_1_00.zip under the 1.23 release). I have tested it with the latest version of Alteryx. Our version of Jira is 7.11.2, so not the latest. But it uses Jira's own Python package to make requests, so I assume it can handle multiple versions of Jira without a problem.
You can provide a JQL string to filter issues upfront and it pulls multiple types of objects (projects, issues, issue sprints, issue components, comments). It's been effective for our ETL needs, maybe you will find it useful as well.