What's your preferred way of work? Especially for work or Atlassian Jira, when you inherit it all from prior colleagues. :) You like to set up everything anew and customize from there, or you rather organise, cleanup and optimise the inherited "mess"? :)

Just dropped a 12 part course that is immediately available to paid members. If you aren't a paid member, no worries, I've set it to unlock the moment you hit Level 3! How do you get to level 3??? Well that part is easy, participate in our community! You earn points when other members like your posts or comments. 1 like = 1 point.

I have observed that many implement the wrong type or style once you deal with structure at large. Whilst rbac is good, I started to lean into abac (pbac) more and want to get better at it. So, conditional access and structure already comes from Entra level or Microsoft side, predefined with attributes and org.policies. Anyone can share how they are integrating this with Jira? Ie. I'd love to continue that an HR ticket from Hibob or similar creates a ticket and with the ticket automation kicks in with MS and populates a new user, etc. I've seen this style or project a few times and wasn't able to study in details. So, what do you/your org prefers? RBAC? Or ABAC? Or Policy based access? Are you familiar with such integration and automation?

How many of you are building"helpdesk" portals , for external users? I would like to understand the differences and issues, if you open a JSM to "invite anyone" vs. "approved/required". What's your best tip for building these open, yet customized portals?

Marketing folks have listed "Asset and configuration management" under the "Standard" tier for the Service Collection here: https://www.atlassian.com/collections/service/pricing What is weird is that they are allowing those who only had JSM standard to migrate early to the Service Collection (with same pricing) or be migrated automatically (sometime this Feb is what it told me). I accepted the Service Collection Standard move from just JSM standard for one of my sites to happen now. This was actually a few days ago. I ended up with "Customer Service Management" but with no access to "Assets" yet. After submitting a support request, they tell me: "...I understand you have a question regarding the 'Assets' Feature within your Service Collection. I know you’re excited to try out this new functionality, and apologize for the inconvenience this has caused. While our features and pricing page does state that Assets is included for Standard plans, please note that there have been some slight delays in getting the feature rolled out. At this time we are targeting an early-mid February release for the Assets feature for all Standard plans. I realize the discrepancy between the information and actual practice isn’t great, and appreciate your understanding. I will pass this feedback along to our team for review as well. There will be a Community Blog post when the feature does officially become available. Please let me know if you have further questions as this time." Also, expanding "Assets pricing" at the bottom of the page at the link above shows a clear contradiction in the first two paragraphs: "Asset and configuration management is included in Service Collection Premium and Enterprise plans. Included in these plans, Standard customers will be allowed to store 5,000 Assets objects for free, while Premium and Enterprise customers will be allowed to store 50,000 and 500,000 Assets objects for free respectively. Above this limit, objects will start at $0.02(USD)/object/month with volume discounts."