Benjamin Paton_yibbj0 Atlassian Team

@Justin S inclusion of Halp/Chat is coming in July. @Paul Bestic @Fiducius User/Customer Account information and data in transit are actively being prioritised (keep an eye on the public roadmap for those).

@Majken Longlade you will be able to have an additional IdP per JSM site. 

Hey @Phill Fox I won't be at TEAM, but I am happy to discuss with you. Is your desire to use the widget, but not have to have the portal set to open? Unfortunately the architecture of the widget requires the portal to be open because it doesn't support authentication. Depending on why you want it closed there might be…

@Ruby Domanico have you seen this article https://community.atlassian.com/t5/Jira-Service-Management-articles/Choosing-the-right-approach-to-Customer-Management-in-Jira/ba-p/1970761? Sounds like you re a hybrid use case. If you restrict internal projects by groups, then your external customers wont be able to see them.

Thanks for the feedback @Todd Thomas I assume the recent increase to 300 queues per project has been well received. Would you have individual team members able to create their own queues? When you say utilise queues further what do you mean? I am sure my colleague @Ash Young would be keen to chat with you further about the…

Hey @Wim Abts By the sounds of it yes. You should be able to connect your Azure AD accounts via SAML and have them authenticate via your Identity Provider. We do not yet support Microsoft accounts for Portal-only Customers, unless they are authenticated via your IDP first. Cheers, Ben.

Thanks everyone. If I have liked your comment I have added you to the EAP list. Please understand that we cannot extend the EAP to everyone, but we will do our best to include as many as possible. @Jason Freeze it sound to me you should be using straight Atlassian Access for all your users. Check out this article and use…

Hey Kalin, Thanks for reaching out. In answer to your questions * You can continue to create an authenticate external customers as you do today. You will be able to add an option identify provider if you want customer to have the freedom to login, or SSO. * If you want to use an SSO directory you will only need to…

Hello all, For anyone following this page, I have just updated some of the roadmap items and timeframes. I have also linked in our latest blog regarding the upcoming SSO capability for external customer accounts Please let me know if you have any questions, Cheers, Ben.

@Thomas Griem https://jira.atlassian.com/browse/JSDCLOUD-4519 this is the best place to watch. @Michael Wood if you are able to add the domains then it should take effect immediately. If it is still not working I suggest raising a support request.

Rollout of the toggle has begun. I have updated the article to reflect the change. Thanks everyone for their patience.

There is one more piece of the puzzle coming later this year, which uses domains to automatically add customers to organisation groups. It sounds like this is the part you are looking for, for controlling access to individual projects. The major capability this feature brings, is the ability to restrict your whole help…

Ok, and do you get the error when this happens, or only when you try and repeat it again? It seems like you need to take a look at your default permissions. That user should not be consuming a seat.

@Mike Vitale it sounds like you have a hybrid strategy for customer management. I recommendation is that you leverage Internal Customer Accounts (also known as Atlassian Accounts) for your Internal team members, I assume they will be using a known list of email domains, so you can utilise the "approved domains" mentioned…

Do you know if the site is at its license cap?

@Ingo Wenke that is right. These settings reside in Product Administration, and as such are decisions that impact all projects in the site.

Letting you all know that a complimentary feature for this one was released today. Allowing you to disable the creation of External Customers accounts when you are using a straight Internal Strategy.…

Quick update here, we have release two more of the features from the list. Rollout starts today! https://community.atlassian.com/t5/Jira-Service-Management-articles/Use-email-domains-to-restrict-external-customer-sign-up-for-your/ba-p/2036372#M1710

@Ryan Geddings this is a good suggestion and is something that we will be considering in the future based on demand. @Suporte JRetail currently these options apply to new customers being created. We will be looking into migration strategies for organisations to get their customers sorted correctly.

Quick update on this one. We were unable to commence rollout for this feature last week as originally planned. We are facing some internal delays associated with the recent Atlassian incident. The feature is ready to go, and we will make it available to you as soon as possible. I hope to confirm a specific date this week.…

@Johnson Ip thanks for the additional info, I think @Greg D offers some good suggestions here. Utilising different projects with organisations is the best way to managed this type of separation. I am not sure why you need to assign a component lead, but maybe this could be achieved with different projects, or automation to…

@Lars Stuber @Adam England are your instances using Release Tracks? Its possible that this feature was not deployed for you at the time of writing. It should be available now. You will know by visiting the Jira Admin > Customer access page. If you have the option to check approved domains for Internal Customers then it is…

@Hannes rollout is planned to start on the 25th. Assuming nothing unexpected you will see the change in your instance over the course of that week.

@Lars Stuber by the sounds of it, this feature will help you achieve what you need. When those from the approved domain visit the portal they will have an Atlassian Account created for them, which will push them down the same flow as you mention for users with existing accounts. This also works via email. Both scenarios…

Hey all, Thanks for all the feedback here it is great. I have been working to pull together our dedicated Community Group for discussing all things Customer Management in JSM. We have a thread there seeking further feedback on this feature, and we will be exploring topics more broadly from the recent Best Practise / Vision…

Hello all, Sorry for the delay on my reply here. I have been working to get the group together and I have updated the article to contain a link for it - https://community.atlassian.com/t5/Customer-Management-for-Jira/gh-p/customer-management-jsm We are kicking off with three discussion threads, but will be adding more…

@Emma Hamlin it might be easier if we can chat about it. Please feel free to grab a time in my calendar

Hello all, I want to say a huge thank you to everyone who took the time to provide feedback on this change. Especially those who took the time to meet with me on Zoom to talk about their specific SLA usage. Based on your feedback we have decided to add a configuration to allow you to decide which format is right for your…

@Emma Hamlin I can see your queue view. But I mean the SLA itself. The goal time, and JQL that feeds it.

Hey Emma, If the resolution time is a week this should be displaying with a week from the creation date. Can you share the goal config for this one? Cheers, Ben