A discussion between Ravi Sagar and Milind Gautam focused on tackling a term frequently encountered by new Jira users, students, and freshers: Jira Automations. The core idea is simple: using automation to save time and reduce errors in your work management.
What is Jira Automation?
Jira Cloud Automations is the feature’s name on Jira Cloud. It is a no-code solution designed to eliminate the need for regular manual activities. Automation becomes highly relevant for users who manage work, lead teams, or perform tasks that go beyond basic ticket handling, such as a developer only working on assigned issues.
Prerequisites and Getting Started
While the feature is no-code, it requires a foundational understanding of how Jira works. Ravi Sagar’s initial recommendation is to focus on learning Jira first, and then evaluate current activities to determine which tasks can be automated.
Project administrators have the necessary access to begin creating automation rules. You can find the "automations" section within the project settings of any project. From there, you can create a new rule from scratch or, the highly recommended starting point, use a template. Templates showcase different common use cases and are an excellent way to see what is possible.
When is the Right Time to Implement?
There is no specific right time to start. The decision to implement automations must be requirements-driven, not just for the sake of using the feature. If Jira is already working effectively for collaboration, automation might not be necessary.
Automation should be relied upon when it is needed—specifically when you or your team are performing daily activities manually that could be automated to save time. It’s important to remember that Jira and its automation features are tools; they are not intended to replace human roles like the manager, PM, scrum master, or team lead, who remain responsible for ensuring work is completed.
Powerful Use Cases for Automation
Automation is valuable for replacing manually performed, daily activities. Useful examples include:
- Sending Reminders: Creating new rules to automatically send reminders, replacing the manual process often done by project coordinators or junior PMO members.
- Notifications: Using templates to send notifications when a sprint starts or is completed.
- Issue Resolution: Automatically closing the parent issue when all associated child issues are complete.
The decision to use automation depends entirely on your team’s specific requirements. The best way to move forward is to explore the variety of automation templates available in your Jira instance to see how they can apply to your workflow.
We have plenty of free videos related to automation rule.
