Hello and welcome @Babar Brohi
It would be helpful if you narrow more for what you looking for?
My rule of thumb is to start with the simplest possible automation and only add complexity when there is a clear benefit.
In Jira, a lot of repetitive work can already be handled with native automation, for example:
field change → update another field
transition → assign / comment / notify
scheduled rule → reminders or cleanup
What usually works best for me is: keep each rule focused on one purpose, use conditions instead of building very large branching logic, and check the audit log before making the rule more advanced.
Atlassian also notes that more complex rules can increase queue load significantly, so keeping rules small is not only easier to maintain, but often better for performance too.
So this is more my own recommendation than an official Atlassian “best practice”, but I would say: automate repetitive steps, not entire decision trees.
Native automation is usually enough for the repetitive 80%, and that is where I would start before bringing in additional apps.
Hope I can help you a little. 🤠
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.