Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Cloud functionality comparison between JMWE and Automation Pro

Hi, my company is currently moving to cloud and one of the things that's happened/happening is a a review of all our add-ons.

Does anyone have experience in comparing JMWE and Automation Pro for conditions/validations/post-functions that must be done in JMWE and cannot be "translated" to automation rules? I know there are a things Nunjucks & Jira Expressions are required for, but we are trying to move to a more self-service model for our project admins. Previously we only had Automation Lite in server but are purchasing the Pro version in cloud.

Some background: we are getting rid of Deviniti's Issue Templates and replacing entirely with Automation. Also, as we prepare for our migration week(s) we are hoping to minimize the amount of work changing over Groovy and other non-compatible functions in JMWE. If we can replace a large part of these things with Automation it would be a major shift that can provide a huge benefit to our team and project admins.

Thanks so much for any advice!



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events