Hi @archana986 ,
If you right click on the macro in your workflow, you should be able to select "Open Macro: JIRA Connector.yxmc". This will open up the workflow for the macro. In terms of changing the limits, under the Project & Issues tab, change the "Starting With" value to the next number after the last record that was downloaded in your previous run.
Hi @TarunDeep ,
The macro is set to import to your Connectors folder in the Tool Palette. If you right click on the macro and open the workflow, you can view the Meta Info in the Workflow - Configuration pane, and under Tool Palette, you can change the "Category Name" from "Connectors" to the name of your macros folder, if you would prefer for it to appear there.
Have you run this connector tool recently? I have been getting an API error message recently and just wanted to confirm that someone has run it successfully so that I can rule out that Atlassian is blocking.
Here is the error I'm getting:
Error: JIRA Connector (1): Tool #227: JIRA API error --> HTTP/1.1 200 Connection Established Proxy-Agent: Zscaler/5.6 HTTP/1.1 401 Server: AtlassianProxy/18.104.22.168 WWW-Authenticate: OAuth realm="https%3A%2F%2Foneamerica.atlassian.net" Content-Type: text/html;charset=UTF-8 Strict-Transport-Security: max-age=315360000; includeSubDomains; preload Date: Thu, 16 May 2019 17:29:58 GMT ATL-TraceId: 2bcff862da711c80 X-AREQUESTID: 63eb2ec7-1b69-4eb5-8c24-910082464893 X-XSS-Protection: 1; mode=block Transfer-Encoding: chunked Timing-Allow-Origin: * X-Content-Type-Options: nosniff Connection: keep-alive X-Seraph-LoginReason: AUTHENTICATED_FAILED Proxy-Support: Session-Based-Authentication
Can you connect to the Jira instance with a curl command? A command something like this will return 5000 rows in a json file format.
curl -u userid:password -X GET -H "Content-Type: application/json" 'https://jira.server.com api/2/search?jql=project=Project-in-Question+AND+issueType=Bug+order+by+createddate+ASC&startAt='$n'&maxResults=5000&expand=names,schema,operations,editmedia,changelog,transitions,renderedFields' > file.json
Your issue looks like Jira isn't set up to accept api calls.
I came across this Atlassian article about API tokens. I followed the steps and swapped out my password with my new token. Good news was I didn't get the error anymore but my projects output set was Null, like it connected but didn't find any projects at all. Frustrating thing is this worked a couple months ago and no one I've talked to seems to know whats going on.