Prince Nyeche - ELFAPP Atlassian Partner

Hey @Adarsh Hegde The users will only loose access to your instance which you've registered with on the app. I'm going to give a thorough explanation so you can get the concept behind Atlassian cloud administration. Each instance must belongs to one organization and an organization can have many list of instances under its…

Is the token encoded in base64 as your email + api token or is it just simply your api token that's there?

Exactly. Give a try to see how it all works.

I would expect it to display only https://secure.gravatar.com/avatar/1212121212?d=https%3A%2F%2Favatar-management--avatars.us-west-2.prod.public.atl-paas.net%2Finitials%2FMB-5.png" Which is the string of the URL and nothing more when accessing the specific key. Except you're still calling it as avatar = avatarUrls 

Why don't you access the JSON key specifically for "48x48"? avatar = avatarUrls["48x48"]

You can open a bug request here and I can look into it as soon as possible. I believe it has something to do with the regular expression but I need to examine it further to know exactly. In the meantime, if it's urgent you can spin up a linux virtual machine on your windows. That way you should be able to use the same…

Hey @Manikanta This problem seems to happen on only windows OS and the version of python seems to vary. Your python version should be version 3.9.x and above. 

Hi, Without domain verification, you cannot manage the users and they will become unmanaged, so provisioning via any identity provider won't work. Also, with Atlassian access there are billable accounts and non billable accounts. When you claim a domain and manage users, it doesn't necessary make all the accounts billable…

You should format the response in your own way that it returns true or false. I believe false response should be when the payload returns an empty list or no value at all. The true response returns a mapping of the data content.

It shouldn't work if it's not accessible over the internet. Remember postman has the ability to interface with your local network, automation for Jira won't do that. What you should do is use a proxy for your Jenkins and put it online then you can send a request to it via automation for Jira.

Hi, Are you certain that there's even a connection with Jenkins at all? I doubt if automation can be able to send data via a local connection as it has to be via the internet, so a 403 response is expected.

Hi You can look into this endpoint for find user with permission. However, take note that you will need to pass an accountId and not username as username are deprecated on cloud. If you want to use an email address, then you will need to have a sort of lookup table where your script or program needs to refer to and get the…

Hi, Are you saying you can find it or you cannot find it? Basically you should be looking at the remote link of an issue to get the confluence link on a Jira issue. I believe that's how you get the link.

Hi One of the conditions required for uploading attachments is that the URL must be public. However it seems that you must have added an additional string to your URL that may be causing this error. See this documentation for the required format.

In a way yes as deleting a Jira user on the cloud basically removes them from your active user management base at the same time revokes access. There're still references to them on other activities such as previous tickets or previous mentions. If you simply want to revoke access but keep the user as a "user without site…

Hi @kumarak I'm not sure about that but if it works for you that's great.

Hi @kumarak It seems that you do not have any events yet in your organization. Make actions in your organization by adding users to groups, creating a new user, etc.

Hi @Alexander kuttner Welcome to community. Please look at the sample code for Java to see an example of authenticating your user using REST API. For example // This code sample uses the 'Unirest' library:// http://unirest.io/java.htmlHttpResponse<JsonNode> response =…

Yes

qm:602xxx accountId is referring to customer-only users from Jira Service Management. It doesn't refer to any other account type apart from JSM customer-only account.

Hi @Gradyn Wursten Try not to rely on email addresses on cloud. By default this is based on the user privacy settings. If you're creating an external app, you can request for the email API, however you have to be a vendor. 

Exactly, getting certified does help in getting proficient in the industry standard of Jira and also everyday usage and problem-solving add more experience which comes over time.

This sounds like something automation for Jira could do by creating some rules. Probably you can try looking into those areas.

The format you used is possible via v2. Mentioning users via v3 is done via its own node in ADF. However, I think for your use case simplify things by using v2.

If it's returning 401 errors, most probably you have not authenticated into the Jira system. You have to solve that problem first by using API tokens within your script.

Hi @Tristan Munthree Please can you create an issue on the package in Github with the stack trace error, so I can trace where the error is coming from?

Hi @Pravin I believe in v2 for servers you can use this format curl -D- -u admin:adminxyz -X POST --data '{"body": "Hi [~XYZ]"}' -H "Content-type: application/json" https://myjira-prod.com/rest/api/2/issue/Test-123/comment

Hi @Pravin I think you're using the API v3 version of mentioning users while calling the v2 endpoint!

Hi @merturi-1 Please can you elaborate on what you tried? * Did you use the shell script? * Was there an error? * Did you create a CSV file with the org name on each line while using the shell script? Elaborating further will let us know how best I can advise you.

Hi @merturi-1 There's a similar answer here provided which you could try.