Jira logo
The #1 software development tool used by agile teams to plan, track, and release great software.
11K
7.3K
1.1K

What is Jira?

Jira's secret sauce is the way it simplifies the complexities of software development into manageable units of work. Jira comes out-of-the-box with everything agile teams need to ship value to customers faster.
Jira is a tool in the Issue Tracking category of a tech stack.

Who uses Jira?

Companies
2672 companies reportedly use Jira in their tech stacks, including Pinterest, Twitter, and reddit.

Developers
7922 developers on StackShare have stated that they use Jira.

Jira Integrations

GitHub, Slack, Bitbucket, New Relic, and Confluence are some of the popular tools that integrate with Jira. Here's a list of all 128 tools that integrate with Jira.

Why developers like Jira?

Here’s a list of reasons why companies and developers use Jira
Jira Reviews

Here are some stack decisions, common use cases and reviews by companies and developers who chose Jira in their tech stack.

Oliver Burn
Oliver Burn
Architect at Atlassian · | 12 upvotes · 46.8K views
atAtlassianAtlassian
Azure Pipelines
jFrog
Octopus Deploy
AWS CodePipeline
CircleCI
Bitbucket
Jira

We recently added new APIs to Jira to associate information about Builds and Deployments to Jira issues.

The new APIs were developed using a spec-first API approach for speed and sanity. The details of this approach are described in this blog post, and we relied on using Swagger and associated tools like Swagger UI.

A new service was created for managing the data. It provides a REST API for external use, and an internal API based on GraphQL. The service is built using Kotlin for increased developer productivity and happiness, and the Spring-Boot framework. PostgreSQL was chosen for the persistence layer, as we have non-trivial requirements that cannot be easily implemented on top of a key-value store.

The front-end has been built using React and querying the back-end service using an internal GraphQL API. We have plans of providing a public GraphQL API in the future.

New Jira Integrations: Bitbucket CircleCI AWS CodePipeline Octopus Deploy jFrog Azure Pipelines

See more
Petr Havlicek
Petr Havlicek
Freelancer at havlicekpetr.cz · | 11 upvotes · 6.2K views
Jira
#Trello

I use Jira because

  • It's used widely as the best SW dev tool
  • It's so easy to use
  • Flexible to configure
  • Great for tracking of tickets while leading meetings
  • Accessible from Everywhere

In overall, especially for large projects, Confluence is must. On the other hands, for small-mid size projects, #Trello is also great due to visualisation power.

See more
David Ritsema
David Ritsema
Frontend Architect at Herman Miller · | 10 upvotes · 9.5K views
atHerman MillerHerman Miller
GitHub
Confluence
Jira

We knew how we wanted to build our Design System, now it was time to choose the tools to get us there. The essence of Scrum is a small team of people. The team is highly flexible and adaptive. Perfect, so we'll work in 2 week sprints where each sprint can be a mix of new R&D stories, a presentation of decisions made, and showcasing key development milestones.

We are also able to run content stories in parallel, focusing development efforts around key areas of the site that our authors need first. Our stories would exist in a Jira backlog, documentation would be hosted in Confluence , and GitHub would host our codebase. If developers identify technical improvements during the sprint, they can be added as GitHub issues and transferred to Jira if we decide to represent them as stories for the Backlog. For Sprint Retrospectives, @groupmap proved to be a great way to include our remote members of the dev team.

This worked well for our team and allowed us to be flexible in what we wanted to build and how we wanted to build it. As we further defined our Backlog and estimated each story, we could accurately measure the team's capacity (velocity) and confidently estimate a launch date.

See more
Priit Kaasik
Priit Kaasik
Engineering Lead at Katana MRP · | 9 upvotes · 13.6K views
atKatana MRPKatana MRP
Papertrail
appear.in
Bitbucket
Confluence
Intercom
Jira
Slack
#RemoteTeam
#Agile
#CustomerSupportChat
#Notes
#SourceCode
#Logging
#Release
#InProductCommunication
#ContinuousDelivery
#Alerts
#Documentation
#Requirements

As a new company we could early adopt and bet on #RemoteTeam setup without cultural baggage derailing us. Our building blocks for developing remote working culture are:

  • Hiring people who are self sufficient, self-disciplined and excel at video and written communication to work remotely
  • Set up periodic ceremonies ( #DailyStandup, #Grooming, Release calls and chats etc) to keep the company rhythm / heartbeat going across remote cells
  • Regularly train your leaders to take into account remote working aspects of organizing f2f calls, events, meetups, parties etc. when communicating and organizing workflows
  • And last, but not least - select the right tools to support effective communication and collaboration:
  1. All feeds and conversations come together in Slack
  2. #Agile workflows in Jira
  3. InProductCommunication and #CustomerSupportChat in Intercom
  4. #Notes, #Documentation and #Requirements in Confluence
  5. #SourceCode and ContinuousDelivery in Bitbucket
  6. Persistent video streams between locations, demos, meetings run on appear.in
  7. #Logging and Alerts in Papertrail
See more
Priit Kaasik
Priit Kaasik
Engineering Lead at Katana MRP · | 7 upvotes · 35.2K views
atKatana MRPKatana MRP
Sketch
InVision
Slack
Microsoft Office 365
Jira
GitHub
Bitbucket
Confluence

How we ended up choosing Confluence as our internal web / wiki / documentation platform at Katana.

It happened because we chose Bitbucket over GitHub . We had Katana's first hackaton to assemble and test product engineering platform. It turned out that at that time you could have Bitbucket's private repositories and a team of five people for free - Done!

This decision led us to using Bitbucket pipelines for CI, Jira for Kanban, and finally, Confluence. We also use Microsoft Office 365 and started with using OneNote, but SharePoint is still a nightmare product to use to collaborate, so OneNote had to go.

Now, when thinking of the key value of Confluence to Katana then it is Product Requirements Management. We use Page Properties macros, integrations (with Slack , InVision, Sketch etc.) to manage Product Roadmap, flash out Epic and User Stories.

We ended up with using Confluence because it is the best fit for our current engineering ecosystem.

See more
Johnny Bell
Johnny Bell
Sr. Software Engineer at StackShare · | 7 upvotes · 26.1K views
atStackShareStackShare
Markdown
GitHub
Trello
Jira
#Agile
#StoryPoints
#TrelloPowerUps
#StackDecisionsLaunch
#Startup
#Kanban
#Massive

So I am a huge fan of JIRA like #massive I used it for many many years, and really loved it, used it personally and at work. I would suggest every new workplace that I worked at to switch to JIRA instead of what I was using.

When I started at #StackShare we were using a Trello #Kanban board and I was so shocked at how easy the workflow was to follow, create new tasks and get tasks QA'd and deployed. What was so great about this was it didn't come with all the complexity of JIRA. Like setting up a project, user rules etc. You are able to hit the ground running with Trello and get tasks started right away without being overwhelmed with the complexity of options in JIRA

With a few TrelloPowerUps we were easily able to add GitHub integration and storyPoints to our cards and thats all we needed to get a really nice agile workflow going.

I'm not saying that JIRA is not useful, I can see larger companies being able to use the JIRA features and have the time to go through all the complex setup to get a really good workflow going. But for smaller #Startups that want to hit the ground running Trello for me is the way to go.

In saying that what I would love Trello to implement is to allow me to create custom fields. Right now we just have a Description field. So I am adding User Stories & How To Test in the Markdown of the Description if I could have these as custom fields then my #Agile workflow would be complete.

#StackDecisionsLaunch

See more

Jira Alternatives & Comparisons

What are some alternatives to Jira?
Trello
Trello is a collaboration tool that organizes your projects into boards. In one glance, Trello tells you what's being worked on, who's working on what, and where something is in a process.
Asana
Asana is the easiest way for teams to track their work. From tasks and projects to conversations and dashboards, Asana enables teams to move work from start to finish--and get results. Available at asana.com and on iOS & Android.
Confluence
Capture the knowledge that's too often lost in email inboxes and shared network drives in Confluence instead – where it's easy to find, use, and update.
Redmine
Redmine is a flexible project management web application. Written using the Ruby on Rails framework, it is cross-platform and cross-database.
Bugzilla
Bugzilla is a "Defect Tracking System" or "Bug-Tracking System". Defect Tracking Systems allow individual or groups of developers to keep track of outstanding bugs in their product effectively. Most commercial defect-tracking software vendors charge enormous licensing fees. Despite being "free", Bugzilla has many features its expensive counterparts lack.
See all alternatives

Jira's Stats

- No public GitHub repository available -

Jira's Followers
7300 developers follow Jira to keep up with related blogs and decisions.
Cody Brown
Arun Kumar
grijos
Oluwafemi Medale
Lucky Jack Aubrey
Alex Stokoe
Sangmin Lee
Ruchika Datir
Masunar
Edson José Lima Junior