Rodrigo B. Atlassian Team

Just a thought and eager to hear from someone that has tried or is willing to try it: Some companies manage the web browser used by their employees, this is an example of how you can blocklist certain URLs using Chrome: https://support.google.com/chrome/a/answer/7532419?hl=en#zippy=%2Clinux Would that be a viable option,…

Hi @Oto Tabares Thanks for reporting that, as the article is from 2020, it's possible that something changed. May I ask some clarifications? When you say that users gain agent access if they have Jira licenses, are those Jira Service Management licenses, or other Jira types? Thanks!

Hi @Benjamin Kister I know it's been a long while, but for the sake of all people that find this question in the future, here is a diagnosis of mine for this problem: Looking at the HTTP request sent by the browser to upload the file, which uses the endpoint "/rest/jira-importers-plugin/1.0/AttachTemporaryFile", I noticed…

Thank you for the kind words, Aaron! It makes me happy to know that my article helped you, I will keep it up!

No need for automations, the permissions above should be sufficient, but share any challenges you had when applying the instructions!

Hi @Prasad Dintakurthi There is currently no way to customize the project details page, Jira does not have the custom field for projects capability native, hence the recommendation of using an add-on. Rodrigo Becker

Hi @Prasad Dintakurthi You might be able to achieve your goal using the same suggestion above with the Profields add-on, did you find any blocker to use the add-on for this purpose as well? We believe you can create multiple custom fields for the projects. Thanks, Rodrigo Becker Atlassian Cloud Support

Hi Lloyd, We only provide SAML as the means to integrate with other Identity Providers on the Cloud for SSO, SAML is a feature from Atlassian Access, hence you would need to subscribe. Access has some additional features that might be useful for you too, such as user and group provisioning through SCIM, overall audit logs…

Hello everybody who is still watching this question, Atlassian has provided an official guide for the integration: https://confluence.atlassian.com/cloud/configure-saml-single-sign-on-with-active-directory-federation-services-ad-fs-975020616.html Also, we must thank @Bill Webster for sharing his own guide for the…

@pbraund , it will be the normal flow to configure the SAML integration, all of your users that do not have any product licenses will not count for the Atlassian Access bill automatically, you can actually subscribe for the Atlassian Access trial and export a CSV from your Atlassian organization's managed accounts where…

Hi @pbraund Can you confirm if the accepted answer to this question covers your concerns? It references the licensing FAQ for Atlassian Access confirming that Atlassian accounts without product licenses won't be charged. 5. Are Jira Service Desk customers billable? No, Jira Service Desk customers that submit tickets are…

Hello @Marthine & @Chad Mellon Apologies for any delay to get back to you with an answer, it seems I missed to be more specific about my initial answer to all of your questions and that was my mistake, so here you go: There is already one for the confluence space, the regular Jira app and Strike?! or something like that.…

Thanks for mentioning me here @Stéphane Veraart - Really missed it!

Hi @Natalia Lezhai, Yes, per limitation, the second org will have to be created by an user that is not an org admin already and is a site-admin on any Cloud site, but once the org is created, the org admins from the other org can be added to the second one as org admins as well, if required. Kind regards, Rod

Hi Stéphane, Great question! Unfortunately the Atlassian Access product is for the Cloud only, its features are designed to interact exclusively with the Cloud architecture, so it can't be used as a service for Server/Data Center, currently there are no plans on our roadmap to model Atlassian Access for these platforms.…

No problem @Jackson Lum, thanks for the confirmation!

To log in with Google is a feature available to all Atlassian accounts that are Google based, they can still log in using the Atlassian account credentials too. The difference is that with G Suite, the users are enforced to log in with Google Auth, they won't be able to log in using the Atlassian account's credentials. I…

Hi @Ian Walsh, Yes, otherwise Jira/Confluence notifications would go nowhere and also, if the user sends an email to the project email to create an issue or comment, it would not be accepted as the email from the sender would not match any email with the proper permissions on the instance. RB

Hey @Jackson Lum and @Ian Walsh, Yes and big no, the big no is because if other departments are using Jira or Confluence as well, they will be forced to use SSO without their acknowledgement, because they would be under the same verified domain probably, so it will raise some confusion. Yes goes for when that is the only…

Hi @Adrian Ang, Your suspicion is right, unfortunately the user being disabled on the SSO will not cause it to be disabled on Jira as well, the user won't be able to access your Jira anymore through SSO, but the license seat will still be used. To allow this kind of synchronization, we are developing the necessary means…

Hi Jackson, I see Kenta answered your question, since it's accepted, I will just wish you a great day ahead! Thanks, Rodrigo Becker

No problem @Jackson Lum, happy to help! If you're good, just make sure to accept the answer so others in the community can see it had a solution and benefit as well! Rodrigo

It's not possible to share the same domain, a domain can only be claimed by a single Atlassian organization. The billing and licensing works this way, each instance has it's own billing, for Jira or Confluence, etc, an Atlassian Access subscription is also a separate licensing/billing, so it would look this way: ACME1 -…

Hello @Jackson Lum, Welcome to our community! Answering your question, yes, you can have multiple instances authenticating to your Single sign-on (SSO), this happens because you will have an Atlassian organization which is a global entity, once you verify a domain, all existing Atlassian accounts that have their emails…

It's not possible, the integration is done using the SAML feature, without that, you would lose both enforced SSO authentication and the profile sync, SAML is the bridge between your Identity Provider and your Atlassian organization. Okta does provide an unsupported method by using SWA protocol instead of SAML, you would…

The Atlassian Access subscription will be separate from your Cloud site subscription, you can check it on the Billing menu on the admin.atlassian.com as well to see how much is the estimate and when your trial will end. The SAML integration's scope is to force users to authenticate through your Identity Provider (Okta) as…

Hi @Jeanne Howe, If the integration was done using the SAML feature, then it's done through Atlassian Access as this feature is only available on the product, you can check on that by going to your Atlassian organization on admin.atlassian.com and clicking on the SAML single sign-on, if the feature is enabled and there is…

Hello @Adibou, The current public APIs for users are only related to the products themselves and not our Identity Platform (Where the Atlassian accounts are) to perform actions such as Disable the entire Atlassian account or edit user details. This set of APIs demand for an extra security layer, so we are developing public…

Yes, you can do that!

@Amalinally De La Rosa, Re-reading again I noticed this statement may cause some confusion: it's one time cost per user This means that you won't pay more for each product or service this user uses, but it's still tied to a monthly or annual subscription. Apologies for not being clearer. Rodrigo Becker Atlassian Cloud…