I don't mean the general Jira Cloud/Server/DC differenes, but specific JSM feature differences, natively, out of the box, no additional purchases.
For example, JSM Cloud benefits from Automation for Jira built in, where DC users still need to purchase the tool.
Are there features in one missing in the other?
@Dave Liao 's link is an excellent references to your ask. Opsgenie is another element that comes out of the box in JSM Cloud and not for JSM DC. Regarding to Automation for Jira element (JSM Cloud env) is only for Premium accounts.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Viasat Inc.
You sure about that? My free JSM says otherwise, and redirects me to a link about Legacy Automation. I'd be happy to share it if the community message board wasn't blocking every attempt.
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.
Agreed with @Rob Horan - Free Jira instances have access to Automation.
Of course, the paid Premium and Enterprise plans let you make automations that apply to multiple projects, or globally, if desired.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks - I'm very curious as to what these new rules will look like once they are converted from Legacy to standard Jira Automation.
As far as I can tell there are no limits to how many times project-specific rules can be run, so I don't see any issues with transitioning from Legacy Automation in that regard.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Rob Horan - agreed.
As someone with experience with both the legacy Automation (de facto on JSM on-prem) and the Automation add-on, I know they'd be easier to edit, and that we get a better pile of automation LEGOs to play with. 😆
This will also make it easier for Jira stewards when working with project-level admins. Having to explain "legacy Automation" vs "Automation" is a chore.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Rob Horan - FYI, if either/both of our answers help you out, feel free to "Accept" them! I get a cookie every time someone accepts my answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks! I thought I had accepted the answer earlier, so thanks for the reminder! (I like my kudo points as well)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Rob Horan - off the top of my head:
Hmm, I should write an article on this.
Actually, I searched online and there IS an Atlassian support article (updated in March) highlighting some differences, including features JSM Cloud does not have yet:
Hope this helps!
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.