Prince Nyeche - ELFAPP Atlassian Partner

Hi @Sam Becker Batched email is available on cloud for Jira notifications. If you have JSM and expecting batch notifications for customers then that's not feasible.

Hi @Gunta S Thanks for confirming that. From the trace above, it seems as though you've entered the wrong password or username a couple of times and Confluence has returned a captcha screen which is not visible on terminal. X-Seraph-LoginReason: AUTHENTICATED_FAILED Try the below curl example curl -v \ --url…

Hi @Gunta S Welcome to community! Do you use any form of 2FA to authenticate users on your Confluence server?

As @Jack Brickey mentioned it's not OOTB but that would be a nice feature to have with Atlassian access.

Hi @Pete Piro Welcome to community! Do you know if the customer already exist within that organization? And what error do you see on your screen?

Hi @Lewis Everly Just to add in here. When making api request to Jira is good to know how many request you can make out. Making 2 request per minute should be the max that you go for to avoid this error.

Hi @Daniel Palermi You will need to generate an API key here and it only last for 7 days. Authentication uses auth bearer Authorization: Bearer <access_token> You don't need an email address, you just simply need the token placed in that format above. See more for the documentation Please note that accessing Atlassian REST…

There shouldn't be an issue. I'm assuming the 40k accounts are referring to customer only accounts? Then I would suggest you use the filtering of "accountType": "customer" This way you can get only customer only account rather than agent or Jira user account.

Hey @divya The API doesn't return the total number of user's available, you can get that from the record count.You can create a function that will produce the desired result you want. The API would just return the user's details only.

Hi @Bruce Hartman There are various solutions available. You can code in virtually any language and use externally to the cloud environment by making API calls to it. Others includes using automation for Jira within you cloud instance to handle this type of task you've mentioned. Standard Jira permission applies to any…

Hi @divya You need to use pagination in your code. You can use the startAt parameter to search record by record. Run a loop and only stop the loop when you reach an empty list like [] from the payload.

Hi @Pavlo Shynal Please can you remove the image above as it contains email address of your users. The reason why you get that error is because for you to remove an Org admin, you will need to first remove the Org admin ability from your settings as show on the below image. After that, go to your user hub…

So if it's still showing you that, it's one of the two mentioned conditions above.

Hey @Chris Zollinger Are you certain you have verified your domain and have Atlassian access subscription? Those are the two main conditions to check.

Then you should be able to see it under security from your Admin hub.

None that I know of. I think if the API doesn't exist then you can't basically do it.

I think you need to elaborate a little more here.

Hi @Chris Zollinger Do you have Atlassian access subscription? As you may want to know that's a feature that comes when you actually purchase and pay for Atlassian access.

Hi, you have to filter the result. Atlassian cloud has 4 different accountType namely: * customer > for JSM customer users * atlassian > for any Atlassian cloud user * app > for any app on Atlassian cloud * unknown > for any unknown users such as oAuth integration or there about. Knowing the above, you should filter your…

Glad to hear that.

Hi @[deleted] Have you tried using the Unirest library for Java to perform authentication?

Hi @Joao Zampa Welcome to community! While using the search user endpoint, rather than calling one user at a time by defining an email, don't use the query parameter. Instead use the startAt parameter (which searches record by record) and run a loop to call all user and filter the data by "active" status. "active": false…

Hi @Pavlo Shynal Just to expand on this, deactivation is the way to go or just remove the product access from the user so it doesn't count towards a license. Product access refers groups that are given application access to Jira. You can do this from the "Admin hub". There are many issues that may arise as a result of a…

Hi @Heberto Lorenzo If the users already exist on Atlassian cloud, you should claim your domain and when you link Atlassian access to Okta via SAML SSO that should sync the users into Okta. I believe that's the way it works.

Hi @Ahsan Zaman Welcome to community! It seems you've configured your goals and set up the filters for your SLA. What you should do next is set up conditions on how those times will be measured and what action you want the SLA to perform when met.

Hi @Vivek Welcome to the community! I don't think those attributes can be changed with the API yet.

Hi @sushanth_shettigar You need to be an admin before you can query an api to list all the users on the instance. However, knowing which user is admin or not depends on your user group. You can use the group api to determine if a user is in a certain group to differentiate if they are admin or normal users. Check your Jira…

Hi, I provided the api to list the user roles above. However to get the users, you will need to combine multiple apis to achieve that. 

Hi @divya Welcome to community! You can use the users api to fetch users and add users in your instance. However, regarding billing related information. Are there any specific information you're looking for?

Hi @Carol Rodriguez Adding users per project from the people's tab of your project settings is not a scalable approach .You should consider adding the users to a group then adding that group to a project role. That way you can easily manage the user list. If added on a single user basis, it becomes a nightmare in future.