You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are looking forward to implementing AWS OpsItems into Jira Service Management Cloud. Ideally, we want the JSM to create a ticket automatically when AWS OpsCenter raised an alarm right away. The tutorials online do not suit the JSM Cloud version :)
Fortunately AWS has recently released the Cloud version of their well documented and maintained AWS Service Management Connector for JSM, and it seems to have more or less feature parity with the Data Center version.
This doesn't answer the question, but I think it's worth pointing out that the meanwhile renamed AWS Service Management Connector for JSM Data Center maintained by the AWS team has decent documentation, gained quite some features over time, including the requested capability to "Create and update a Jira Issue when you create and update an operational item (OpsItem) in AWS Systems Manager OpsCenter" (see release notes).
In contrast, the sibling app AWS Service Catalog for JSM Cloud maintained by the Atlassian team still uses the original name, has only abysmal documentation, launched with less features to boot, hardly gained any features since its release, and seems poorly maintained even as per the respectively bad reviews.
I always wondered what drove the odd decision to release and maintain these sibling apps via two different organizations with notably different product development philosophies (their strategic partnership notwithstanding), and the disconnected outcome in scope and quality confirms my expectation, unfortunately.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, any further advice or updates on the topic?
So far I have found Zapier and Tray.io as possible solutions, but I am still exploring, so not 100% sure they will work.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Joe Killian Welcome to the Atlassian Community
If you can have the alarm just send an email that would be the easiest. If you can not send an email then you will want to use the API https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.