Prince Nyeche - ELFAPP Atlassian Partner

Tried it and it works for me using automation, I get a 200 response. This is where you retrace your steps and revalidate your entire rules from scratch on the API. You also might want to try the remote link endpoint via curl and if it works via curl then most probably, it's not because it's a free tier.

Do you add the headers as Authorization Basic Base64encodedString OR Authorization Bearer Base64encodedString However, you say this works for GET issues. Which seems weird, if such errors are there.

Your JSON object returned "None" hence that error. When that happens, the JSON decoder can not parse NoneType objects. Probably you want to make sure that you're authenticated properly before running the user search. You can use /rest/api/2/myself to give a test and see the type of response your server returns

I will suggest reviewing your permission scheme after checking your field screens to ensure those fields exist there.

You need to have the Confluence application on the same instance as well as permission on the Confluence to link to it from the Project pages.

That means you're sending something the server understands but rejects. What you can do is output the error message for a better understanding of the 400 errors.

From your code, you seem to be encoding and decoding which is wrong. If you're downloading content from Jira, the response will be in bytes, you simply just need to write that content into a file object.

I don't think this feature exists yet. You can follow this feature request https://jira.atlassian.com/browse/JSWCLOUD-17631

You should look into the official documentation for proper formatting. There are examples shown there. I believe it should come with a prefix "jira:"

Hey @Hector Eduardo Calzada Tenorio About the previous issue, you can download the latest version of jiraone to fix that problem. Let me know how that goes.

Hey @Hector Eduardo Calzada Tenorio I don't have this yet on jiraone but a report can be constructed with jiraone by calling multiple APIs but I think you're referring to a simple call or function to get this kind of report data. If that's the case, I can add work log data as part of an additional feature report but all…

Probably you can ask more about this from https://developer.atlassian.com/support 

Are you able to edit the issue field? Check if you have permission for that.

Are you referring to getting the value of a specific field within the Jira issue?

The webhooks created via REST API and the one from the add-on descriptor are basically the same thing. It is just the different ways of registering it. To refresh it, you can call this endpoint.

You're using an old doc. Cloud instances deprecated username. Therefore, you should use accountId if you want to add watchers to an issue. See this official doc for an example.

There shouldn't be any time delay in such action. In any case, a proper refresh should do it.

You should get started here

I don't think so, as there isn't one mentioned in the API docs. Probably might require going through the issue itself.

Hey @Edward.Davies You will need to sign up for an account then use that account to login into the app. There's a guide here which shows you how to do it. Once you're logged in, generate an API token from here which you need to add to the app before performing any action.

Refer to this API for field option value.

Not possible via REST and I don't think this is something that should be allowed in the first place on Jira. The history is like an integrity checker. If the data can be easily wiped or changed without a trace of what the previous item was, it can compromise a lot of organization security that uses such means as a way to…

Yes, that's it.

Hey @Robert Rodrigues I did a patch of the code which you can use instead rather than rewriting the headers as the headers shouldn't be written to the file and the call shouldn't be updating the list all the time as that takes time when you're running larger dataset. With this behaviour, it creates the file once when…

Okay, I think I know the reason why.Since the call to USER.search_user happens consecutively, there's a rewrite of the file and the self.user_list stores all the entries. Somehow it takes the keys of ordered dict values and appends that when rewriting the file hence this problem. Changing the code as a workaround is okay…

I don't think that was the cause. The for loop is suppose to receive the data after being read from the file and the file is written by searching get_all_users method. Looking at the file you've shown, it seems that the failure occurs when trying to read row 2. For some reason, the file itself is mutated with a header. Now…

Yes, it seems to have one less item in the record at that point in the code. A header is created to ensure what is received matches the header column item. I think the problem might lie on the list_user variable that's reading the user list within the USER.search_user method. You should see a folder and CSV file created…

If you're using cloud, you should reach out to Atlassian support to help unblock the email.

That content should be in bytes. You're getting binary string data. What you should do is write that content into a file data structure if you simply want to get the file data. If you want to convert to base64, I believe you could simply just convert the entire structure by decoding it to plain strings prior to using…

Hey @Robert Rodrigues The USER.search_user() method does an exact string match of the displayName. It does not use any regular expression to pin point potential matches. The reason it returns 0 is because it couldn't find the user from the string used. Most probably, the string that is being used as the search term isn't…