Project and issue tracking
Enterprise agile planning
Essential business management
Modern incident response
Collaborate visually on any project
Git code management
Git and Mercurial desktop client
Integration and release management
Security and control for cloud
User management for self-managed environments
Apps that enhance Atlassian products
Docs and resources to build Atlassian apps
Compliance, privacy, platform roadmap, and more
Stories on culture, tech, teams, and tips
Great for startups, from incubator to IPO
Get the right tools for your growing business
Learn how we make big teams successful
Plan, build, & ship quality products
Bring together a winning strategy
Streamline people management
Operate securely and reliably
Run your business efficiently
Provide great service and support
Simplify all finance processes
Respond, resolve, & learn from incidents
Guides to all of our products
Changes to server and Data Center
Tools and guidance for migrating
Upcoming feature releases
FAQs about our policies
Personal support for large teams
Trusted third-party consultants
A resource hub for teams and admins
Our mission and history
Job openings, values, and more
Training and certifications for all skill levels
A forum for connecting, sharing, and learning
It is not just software teams that use Jira. In fact, 9 out of 10 people who use Jira automation are not developers.
Below are a few of the common use cases we have seen business teams (including Project Managers, HR, legal and marketing teams) use. All can be completely customized to your own needs.
Using a scheduled trigger, seek out old Jira issues and delete their attachments. Perfect for those with a passion for compliance & GDPR.
This is a rule commonly used by HR teams to automate the process of new hires or making sure you tick all the boxes when an employee is leaving.
Whenever a confidential issue is created, then edit the security level and comment on the issue. Legal teams, in particular, use this rule.
Whenever a ‘webinar’ issue is created by marketing, automatically create a design ticket with specs and a landing page ticket. Then link them altogether.
Just like developers, good designers like to stay in focus mode. This rule automates the approval process and updates the team so the designer doesn’t need to.
This rule is a good example of how a finance team can automate the checking of expense claims. Any issues that are in a certain status but have no attachments? Email the owner to remind them.