Alternatives to Jira logo

Alternatives to Jira

Trello, Asana, Confluence, Redmine, and Bugzilla are the most popular alternatives and competitors to Jira.
38.7K
28.5K
+ 1
1.1K

What is Jira and what are its top alternatives?

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.

Top Alternatives to Jira

  • Trello

    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

    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

    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

    Redmine is a flexible project management web application. Written using the Ruby on Rails framework, it is cross-platform and cross-database. ...

  • Bugzilla

    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. ...

  • GitHub

    GitHub

    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together. ...

  • Microsoft SharePoint

    Microsoft SharePoint

    It empowers teamwork with dynamic and productive team sites for every project team, department, and division. Share and manage content, knowledge, and applications to empower teamwork, quickly find information, and seamlessly collaborate across the organization. ...

  • Pivotal Tracker

    Pivotal Tracker

    It is a collaborative, lightweight agile project management tool, brought to you by the experts in agile software development. ...

Jira alternatives & related posts

Trello logo

Trello

32.1K
23.7K
3.7K
Your entire project, in a single glance
32.1K
23.7K
+ 1
3.7K
PROS OF TRELLO
  • 716
    Great for collaboration
  • 625
    Easy to use
  • 571
    Free
  • 375
    Fast
  • 347
    Realtime
  • 237
    Intuitive
  • 214
    Visualizing
  • 169
    Flexible
  • 126
    Fun user interface
  • 84
    Snappy and blazing fast
  • 30
    Simple, intuitive UI that gets out of your way
  • 26
    Kanban
  • 19
    Clean Interface
  • 18
    Easy setup
  • 18
    Card Structure
  • 15
    Drag and drop attachments
  • 11
    Simple
  • 10
    Markdown commentary on cards
  • 9
    Lists
  • 9
    Integration with other work collaborative apps
  • 8
    Cross-Platform Integration
  • 8
    Satisfying User Experience
  • 7
    Recognizes GitHub commit links
  • 6
    Easy to learn
  • 5
    Great
  • 4
    Versatile Team & Project Management
  • 3
    and lots of integrations
  • 3
    Trello’s Developmental Transparency
  • 3
    Better than email
  • 3
    Effective
  • 2
    Easy
  • 2
    Agile
  • 2
    Powerful
  • 2
    Easy to have an overview of the project status
  • 2
    flexible and fast
  • 2
    Simple and intuitive
  • 1
    Personal organisation
  • 1
    Customizable
  • 1
    Email integration
  • 1
    Name rolls of the tongue
  • 1
    Nice
  • 1
    Great organizing (of events/tasks)
  • 0
    Easiest way to visually express the scope of projects
CONS OF TRELLO
  • 5
    No concept of velocity or points
  • 4
    Very light native integrations
  • 2
    A little too flexible

related Trello posts

Johnny Bell
Software Engineer at Weedmaps · | 17 upvotes · 622.4K views

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
Francisco Quintero
Tech Lead at Dev As Pros · | 13 upvotes · 700K views

For Etom, a side project. We wanted to test an idea for a future and bigger project.

What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.

You kind of need a map to work as a proxy between the software and Google Maps API.

We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.

Thanks to all the people behind Create React App it's easier to start any React application.

We also chose a module called Reactstrap which is Bootstrap UI in React components.

An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to

Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.

See more
Asana logo

Asana

6.5K
4.6K
652
Enabling the teams to work together effortlessly
6.5K
4.6K
+ 1
652
PROS OF ASANA
  • 160
    Super fast task creation
  • 148
    Flexible project management
  • 101
    Free up to 15
  • 99
    Followers and commenting on tasks
  • 57
    Integration with external services
  • 25
    Email-based task creation
  • 17
    Plays nice with Google Apps
  • 14
    Clear usage
  • 13
    Plays nice with Harvest Time Tracking
  • 6
    Supports nice keyboard shortcuts
  • 4
    Integration with GitHub
  • 2
    Slack supported
  • 2
    Integration with Instagantt for Gantt Charts
  • 1
    Integration with Alfred
  • 1
    Both Card View & Task View
  • 1
    Easy to use
  • 1
    Friendly API
  • 0
    Slick and fast interface
CONS OF ASANA
  • 0
    Not Cross Platform

related Asana posts

Lucas Litton
Director of Strategy at DigitalSignal · | 22 upvotes · 92.8K views

Sentry has been essential to our development approach. Nobody likes errors or apps that crash. We use Sentry heavily during Node.js and React development. Our developers are able to see error reports, crashes, user's browsers, and more, all in one place. Sentry also seamlessly integrates with Asana, Slack, and GitHub.

See more
Shared insights
on
Jira
Asana
Trello
Aha!

I'm comparing Aha!, Trello and Asana. We are looking for it as a Product Management Team. Jira handles all our development and storyboard etc. This is for Product Management for Roadmaps, Backlogs, future stories, etc. Cost is a factor, as well. Does anyone have a comparison chart of Pros and Cons? Thank you.

See more
Confluence logo

Confluence

16.3K
11.1K
196
One place to share, find, and collaborate on information
16.3K
11.1K
+ 1
196
PROS OF CONFLUENCE
  • 93
    Wiki search power
  • 61
    WYSIWYG editor
  • 41
    Full featured, works well with embedded docs
  • 1
    Expensive licenses
CONS OF CONFLUENCE
  • 2
    Expensive license

related Confluence posts

David Ritsema
Frontend Architect at Herman Miller · | 11 upvotes · 569.1K views

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
Engineering Lead at Katana MRP · | 9 upvotes · 417.1K views

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
Redmine logo

Redmine

523
368
116
A flexible project management web application written using Ruby on Rails framework
523
368
+ 1
116
PROS OF REDMINE
  • 51
    Open source
  • 26
    Customizable with themes and plugins
  • 8
    Powerful custom queries
  • 8
    Integration with code version control like git/svn
  • 6
    Customizable workflows
  • 6
    Integration with email clients
  • 6
    RESTful API
  • 5
    Support for MS SQL Server
CONS OF REDMINE
    Be the first to leave a con

    related Redmine posts

    We were using a hosted version of Redmine to track defects and user stories originally. We migrated to Jira.

    Jira was an easy decision for a number of reasons:

    • It's much more "Scrum ready" straight out of the box
    • It's so much easier to keep a track of progress (I love the reporting)
    • It natively encourages you to adhere to Scrum/Agile/Kanban practices
    • Atlassian has a fantastic DevOps ecosystem when considering the likes of Confluence and Bamboo etc
    • So many integrations!
    • Its UI is so intuitive which makes it an absolute pleasure to use!

    I know there are alot of other tools in this space but not even considering anything else at the moment. Love Jira!

    See more
    Bugzilla logo

    Bugzilla

    79
    100
    6
    Server software designed to help you manage software development
    79
    100
    + 1
    6
    PROS OF BUGZILLA
    • 2
      Free
    • 2
      Open source
    • 1
      Detailed
    • 1
      Easy to use
    CONS OF BUGZILLA
      Be the first to leave a con

      related Bugzilla posts

      GitHub logo

      GitHub

      165.2K
      132.4K
      10.2K
      Powerful collaboration, review, and code management for open source and private development projects
      165.2K
      132.4K
      + 1
      10.2K
      PROS OF GITHUB
      • 1.8K
        Open source friendly
      • 1.5K
        Easy source control
      • 1.2K
        Nice UI
      • 1.1K
        Great for team collaboration
      • 857
        Easy setup
      • 496
        Issue tracker
      • 478
        Great community
      • 475
        Remote team collaboration
      • 444
        Great way to share
      • 436
        Pull request and features planning
      • 139
        Just works
      • 125
        Integrated in many tools
      • 112
        Free Public Repos
      • 106
        Github Gists
      • 103
        Github pages
      • 81
        Easy to find repos
      • 60
        Open source
      • 58
        Easy to find projects
      • 56
        Network effect
      • 55
        It's free
      • 47
        Extensive API
      • 42
        Organizations
      • 41
        Branching
      • 33
        Developer Profiles
      • 32
        Git Powered Wikis
      • 29
        Great for collaboration
      • 23
        It's fun
      • 22
        Community SDK involvement
      • 21
        Clean interface and good integrations
      • 19
        Learn from others source code
      • 14
        It integrates directly with Azure
      • 14
        Because: Git
      • 13
        Wide acceptance
      • 10
        Large community
      • 9
        Newsfeed
      • 9
        Standard in Open Source collab
      • 8
        It integrates directly with Hipchat
      • 7
        Beautiful user experience
      • 7
        Fast
      • 6
        Easy to discover new code libraries
      • 6
        Cloud SCM
      • 5
        Graphs
      • 5
        Smooth integration
      • 5
        Nice API
      • 5
        Integrations
      • 5
        It's awesome
      • 4
        Remarkable uptime
      • 4
        Hands down best online Git service available
      • 4
        Reliable
      • 3
        Easy to use and collaborate with others
      • 3
        CI Integration
      • 3
        Free HTML hosting
      • 3
        Loved by developers
      • 3
        Quick Onboarding
      • 3
        Security options
      • 3
        Simple but powerful
      • 3
        Uses GIT
      • 3
        Unlimited Public Repos at no cost
      • 3
        Version Control
      • 2
        Nice to use
      • 1
        Free private repos
      • 1
        Easy deployment via SSH
      • 1
        Beautiful
      • 1
        Owned by micrcosoft
      • 1
        Free HTML hostings
      • 1
        Self Hosted
      • 1
        All in one development service
      • 1
        Easy to use
      • 1
        Good tools support
      • 1
        Easy source control and everything is backed up
      • 1
        Leads the copycats
      • 1
        Never dethroned
      • 1
        Ci
      • 1
        Issues tracker
      • 1
        Easy and efficient maintainance of the projects
      • 1
        IAM
      • 1
        IAM integration
      • 0
        Profound
      • 0
        1
      CONS OF GITHUB
      • 45
        Owned by micrcosoft
      • 36
        Expensive for lone developers that want private repos
      • 15
        Relatively slow product/feature release cadence
      • 10
        API scoping could be better
      • 8
        Only 3 collaborators for private repos
      • 3
        Limited featureset for issue management
      • 2
        GitHub Packages does not support SNAPSHOT versions
      • 1
        Have to use a token for the package registry
      • 1
        No multilingual interface
      • 1
        Takes a long time to commit

      related GitHub posts

      Johnny Bell
      Software Engineer at Weedmaps · | 77 upvotes · 1.1M views

      I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

      I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

      I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

      Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

      Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

      With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

      If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

      See more
      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 2.6M views

      Our whole DevOps stack consists of the following tools:

      • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
      • Respectively Git as revision control system
      • SourceTree as Git GUI
      • Visual Studio Code as IDE
      • CircleCI for continuous integration (automatize development process)
      • Prettier / TSLint / ESLint as code linter
      • SonarQube as quality gate
      • Docker as container management (incl. Docker Compose for multi-container application management)
      • VirtualBox for operating system simulation tests
      • Kubernetes as cluster management for docker containers
      • Heroku for deploying in test environments
      • nginx as web server (preferably used as facade server in production environment)
      • SSLMate (using OpenSSL) for certificate management
      • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
      • PostgreSQL as preferred database system
      • Redis as preferred in-memory database/store (great for caching)

      The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

      • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
      • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
      • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
      • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
      • Scalability: All-in-one framework for distributed systems.
      • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
      See more
      Microsoft SharePoint logo

      Microsoft SharePoint

      267
      184
      4
      Content collaboration for the modern workplace
      267
      184
      + 1
      4
      PROS OF MICROSOFT SHAREPOINT
      • 1
        Stable Platform
      • 1
        Seamless intergration with MS Office
      • 1
        Great online support
      • 1
        Secure
      CONS OF MICROSOFT SHAREPOINT
      • 2
        Rigid, hard to add external applicaions

      related Microsoft SharePoint posts

      Pivotal Tracker logo

      Pivotal Tracker

      631
      409
      299
      Provides a proven agile project management tool for delivering better products
      631
      409
      + 1
      299
      PROS OF PIVOTAL TRACKER
      • 72
        Agile
      • 57
        Easy to use
      • 50
        Nice UI
      • 36
        Scrum friendly
      • 26
        Simple estimation
      • 21
        Slack Integration
      • 12
        Velocity
      • 8
        Great support
      • 8
        Easy setup
      • 6
        It does the estimation better than we humans
      • 2
        Nice ios app
      • 1
        The right kind of simplicity
      CONS OF PIVOTAL TRACKER
      • 2
        Can't seem to change the number of total points

      related Pivotal Tracker posts

      Nasser Khan
      Product Manager at StackShare · | 4 upvotes · 35.8K views
      Shared insights
      on
      Pivotal Tracker
      Jira
      at

      Over time, as our teams became bigger and projects became more complex, we started to take agile processes more seriously and wanted more advanced (by our standards) project management abilities, like burndown charts, velocity tracking, etc. We also wanted to handle a lot of content management tasks that were primarily done by non-technical teams but often touched engineering.

      After using Pivotal Tracker and Wrike, JIRA ended up being the right choice for us. Its design was flexible enough to do engineering project management, content management and other tasks like product roadmapping effectively. It had all the bells and whistles we wanted (plus many more we never got around to using). Given that it is a flexible service that tries to do everything, it is ideal for a team that can 1) dedicate significant bandwidth to upfront setup and organization and 2) empower admins to establish and enforce best practices among team members.

      #Collaboration #IssueTracking #AgileProjectManagement #ProjectManagement

      See more