David Grizzell_7rkg7s Insider

@Alexander Ray it does. The UI on Compass is built more around a DevOps / Operations Manager's view as opposed to the Service Desk Manager view in JSM.

@Alexander Ray you would only need to give a JSM Premium license to the 3 users who don't already have one. Anyone with a JSM Premium license is going to have access to receive alerts, be on call, etc. The other option that Atlassian will be providing more information on is transitioning to Compass which is cheaper. Based…

I don't believe they have shared specific guidance on this yet. What I noticed during the Opsgenie -> JSM merge last year is that the old OpsGenie email collectors continued to work but they advised customers to update to the Jira based email addresses when they had time.

You're on the right track about the features being part of JSM natively now. OpsGenie customers who already used JSM had their instances merged into JSM over the last year or so. It's definitely more feature rich inside of JSM if your incident management process is tightly aligned to your service desk. JSM Premium is going…

For OpsGenie, there is no Data Center option so this transition will be a Cloud-to-Cloud transition to either JSM or Compass. JSM can still be integrated with on-premise solutions like Jira DC and Bitbucket DC in the same manner that OpsGenie does today. Not sure if you are aware, but the FedRAMP Moderate/High compliance…

Hi Alexander, The three main features you mentioned are available in Jira Service Management today. If you don't see them, it may be due to your license type. JSM Premium and up contain the alerting, incident and problem management features. Do you know which JSM plan you are on today? If your OpsGenie instance is under a…

Hi Mike, A few things to verify: * Does the account being used in AWS for the integration have sufficient IAM permissions? * Ensure all of the Fields needed by AWS are configured in the project and issue type where you are attempting to have tickets created. You can verify this in the AWS Service Management Connector…

Awesome, Jeff! Please let me know when you have your first event. I would be happy to come over from Nashville and present or even co-host. I'm glad that the Knoxville Atlassian Community is being revived!

Hey @Jeff Tillett As far as becoming a community leader for Knoxville, if you submit the contact form here it will get the ball rolling. Once you submit, let me know and I will reach out to the Atlassian Community program director to give them a heads up. For venues, let me ask around. You may find places like breweries…

Hey Jeff, I'm not aware of a leader in Knoxville but I would definitely encourage you to organize an event if you are interested. I'd be willing to come present at an event there and could potentially find other speakers or sponsors. I'm originally from that area so still have a few connections in the network! Cheers, David

Beyond what @Robert Tang mentions, in general, I suggest making sure you are updated to the latest available release of Confluence as well as patching your O/S. This will put you in a good position so that when the patch is released for this exploit the upgrade will be relatively painless.

Based on the current information, it appears this is limited to on premise versions of Confluence only (server and data center).

@Robert Tang that's the best course of action. We are an Atlassian Partner and have worked with our clients to do the same over the last few hours if they have a Confluence instance exposed to the internet. The best we can do right now.

This is a pretty serious vulnerability with no advanced warning, mitigation, or fix version. Some additional guidance or details on the exploit would be helpful.

We would be interested in Ansible playbooks. Would certainly help - particularly for partners doing a lot of DC deployments.