Prince Nyeche - ELFAPP Atlassian Partner

I believe you're referring to exporting multiple files in excel and each having varying column lengths. Is that the issue?

Hey, @Malli_tech1993 please can you provide more context to your question? If you're referring to a blank instance or an existing instance.

Typically you need to make a continuous call to the same API with the new data set. You can do that in any loop statement if handling the request programmatically. Which would be the best way to do it? or simply just use a free app within the Atlassian marketplace.

You can use $ curl --request GET \ > --url https://<client>.atlassian.net/rest/api/3/issue/ISSUE-3 \ > --header 'Authorization: Basic Base64_email:api_token' I believe bearer only will work if you're using OAuth generated token. As the API key won't work in the issue API. 

Your JSON data seems valid, I'm not sure what might be wrong here. If you're sending via postman probably you want to confirm that the URL you're sending to is actually the right one and also if there's any additional data that is being passed along with your request via the postman.

The error seems to be clear. You are sending a wrong data object to that API. The JSON object isn't formatted properly. You need to get that checked.

Given that this token is passed in the HTTP request header and since HTTP doesn't really specify a limit. Then you should go with what most server does in limitation. It typically uses header sizes within 16K more or less. Therefore I would suggest keeping the max character for the API key under 256 characters.

You don't need to open your instance to the public. The method mentioned is a secure attachment upload done via CSV which requires that you pass an authentication credential in the CSV file you'll upload to your Jira cloud environment. Read the document to get the full context

You need to pass your email+token in each attachment to securely upload an attachment to the Jira issue if these attachments are coming from a secure server. This document explains how to do that. Alternatively, you can always use REST API to add an attachment to issues by creating a script after the issues have been…

You can also use the JQL search to get a list of that information. I believe that's the easiest way to do it even though via API

Use JQL search API to get the number of issues available based on your search criteria.

Hey @Eric Salenc You shouldn't base64 encode the password, it should just be a plain string of your actual password when you're connecting to a Jira Server as the script will generate basic auth for you. Any encoding is handled by the request. jiraConfig = "my_windows_login", "my_normal_password",…

If it's showing a broken image, most probably there's some form of blocking happening. Are you behind a firewall or VPN, you might be blocking some of Atlassian IP ranges? Probably you can check with your Network admin about Atlassian domains or IP ranges that could be whitelisted. 

Hey @Amarnadh Gadde Typically that should not happen but you can attempt the flow again, probably in an incognito window to see if that helps.

You seem to have a required field on the issuetype you're using to create as shown by the error message. "Enterprise Squad: Enterprise Squad is required." You should check your field configuration or workflow validator for that field.

There's a PHP library that incorporates Atlassian REST API, which you can use here. See their example on creating issues to begin. 

Hey, you can use JQL as this is supported in JSM. request-channel-type = api You can see more info on JQL fields.

You could easily use automation for Jira to bulk add a resolution value to those issues via a JQL search and transition them to close. I assume most probably that these issues opened shouldn't be more than 1K issues, so if you can create a rule that does that, then it will solve this immediate problem. Moving forward, it…

The API won't allow such deletion because in terms of Jira context, the issue isn't closed and some work is still going on that's why the 400 error appears. The easiest way to go about this is to find out which issues are open and close them or have the issues resolved. Since the API for deleting users is still…

As the other community members here have mentioned, this is not available on the cloud. If you're looking for a way to export all your issues into a single file without that 1K limit then just use REST API. A typical example of this is well explained in this article.

You need to set the id in an array as a number. The organization field is capable of containing other organization values, so as an array it just needs the value of the organization id. e.g --data '{ "fields": { "summary": "This is createdvia an API call", "issuetype": { "id": "10285" }, "project": { "key": "xxx" },…

You can just use the External system importer to copy the value into the right field using a CSV file. 

Hey @Dania Zaccara Please can you add more context here? The problem is the attachments! Looks like not all the attachment types are managed. I discovered that, for example, .jpg is good but PDF is not. Can you share elaborate examples of the field data that doesn't contain any personally identifiable information or mask…

Use the REST API and generate the report you want.

You should check out the SSL chain to ensure that it's complete.

Is your certificate self-signed?

Have you considered using an issue collector, it's way easier and you can implement it with Javascript.

What type of field (field type) are you trying to update? Depending on the field type, there are specific ways the update should occur. 

No, you're not, it's the character from probably one of the fields within your Jira issues. It is not being appropriately encoded in UTF-8. The file writer converts everything to a string and then attempts an IO process to write it as a plaintext file which it can read later. It's difficult for me to troubleshoot this as I…

Hey, @Agnès Masson-Sibut You should download the new version v0.7.3 which should fix the exception error of encoded characters.