Project and issue tracking
Business team collaboration
Modern incident response
Enterprise agile planning
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
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
Customers are now automating away thousands of hours of work in Jira every month. Below are some of the most common use cases.
The most popular automations are often the simplest so this is a good place for new automators to start.
When an issue is created without an assignee, automatically assign it. Go one better and assign it based on skillset or in a balanced workload.
Whenever a Jira issue is created, automatically create 5 sub-tasks with certain fields populated. Start simple and add depth as you go.
If the sub-task moves to ‘In Progress’ then move the parent issue to ‘In Progress’ also. Always keep your parent and child tasks in sync.
When an issue transitions in a Jira Software project, clone the exact same issue in a Jira Service Management project.
Keep your issues in Jira linked by auto-linking issues based on the conditions you set.
When an issue transitions to ‘In Progress’ then update the issue's due date.