What is Jira and what are its top alternatives?
Top Alternatives to Jira
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 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. ...
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 is a flexible project management web application. Written using the Ruby on Rails framework, it is cross-platform and cross-database. ...
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 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
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
It is a collaborative, lightweight agile project management tool, brought to you by the experts in agile software development. ...
Jira alternatives & related posts
- Great for collaboration716
- Easy to use627
- Fun user interface126
- Snappy and blazing fast83
- Simple, intuitive UI that gets out of your way30
- Clean Interface21
- Card Structure18
- Easy setup18
- Drag and drop attachments17
- Markdown commentary on cards10
- Integration with other work collaborative apps9
- Satisfying User Experience8
- Cross-Platform Integration8
- Recognizes GitHub commit links7
- Easy to learn6
- Versatile Team & Project Management4
- Better than email4
- Trello’s Developmental Transparency3
- and lots of integrations3
- Easy to have an overview of the project status2
- flexible and fast2
- Simple and intuitive2
- Kanban style1
- Personal organisation1
- Email integration1
- Great organizing (of events/tasks)1
- Name rolls of the tongue1
- Easiest way to visually express the scope of projects0
- No concept of velocity or points5
- Very light native integrations4
- A little too flexible2
related Trello posts
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.
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.
- Super fast task creation160
- Flexible project management149
- Free up to 15101
- Followers and commenting on tasks99
- Integration with external services57
- Email-based task creation25
- Plays nice with Google Apps17
- Clear usage14
- Plays nice with Harvest Time Tracking14
- Supports nice keyboard shortcuts6
- Integration with GitHub4
- Slack supported2
- Integration with Instagantt for Gantt Charts2
- Integration with Alfred1
- Both Card View & Task View1
- Easy to use1
- Friendly API1
- Slick and fast interface0
- Not Cross Platform0
related Asana posts
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.
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.
- Wiki search power93
- WYSIWYG editor62
- Full featured, works well with embedded docs42
- Expensive licenses3
- Expensive license3
related Confluence posts
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.
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:
- All feeds and conversations come together in Slack
- #Agile workflows in Jira
- InProductCommunication and #CustomerSupportChat in Intercom
- #Notes, #Documentation and #Requirements in Confluence
- #SourceCode and ContinuousDelivery in Bitbucket
- Persistent video streams between locations, demos, meetings run on appear.in
- #Logging and Alerts in Papertrail
- Open source54
- Customizable with themes and plugins27
- Integration with code version control like git/svn10
- Powerful custom queries9
- RESTful API6
- Customizable workflows6
- Integration with email clients6
- Support for MS SQL Server5
- Time tracking, reports2
- Projects and groups separation1
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!
- Open source2
- Easy to use1
related Bugzilla posts
- Open source friendly1.8K
- Easy source control1.5K
- Nice UI1.3K
- Great for team collaboration1.1K
- Easy setup865
- Issue tracker504
- Great community485
- Remote team collaboration481
- Great way to share451
- Pull request and features planning442
- Just works146
- Integrated in many tools132
- Free Public Repos120
- Github Gists115
- Github pages111
- Easy to find repos83
- Open source62
- It's free60
- Easy to find projects60
- Network effect56
- Extensive API49
- Developer Profiles34
- Git Powered Wikis32
- Great for collaboration30
- It's fun24
- Clean interface and good integrations23
- Community SDK involvement22
- Learn from others source code20
- Because: Git16
- It integrates directly with Azure14
- Standard in Open Source collab10
- Beautiful user experience8
- It integrates directly with Hipchat8
- Easy to discover new code libraries7
- Smooth integration6
- It's awesome6
- Nice API6
- Cloud SCM6
- Hands down best online Git service available5
- CI Integration5
- Quick Onboarding5
- Remarkable uptime5
- Security options4
- Simple but powerful4
- Loved by developers4
- Easy to use and collaborate with others4
- Version Control4
- Unlimited Public Repos at no cost4
- Uses GIT4
- Free HTML hosting4
- Nice to use3
- Free private repos2
- Issues tracker2
- Easy deployment via SSH2
- Easy source control and everything is backed up2
- IAM integration2
- Easy and efficient maintainance of the projects2
- All in one development service2
- Good tools support2
- Free HTML hostings2
- Self Hosted2
- Never dethroned2
- Very Easy to Use2
- Easy to use2
- Leads the copycats2
- Owned by micrcosoft53
- Expensive for lone developers that want private repos37
- Relatively slow product/feature release cadence15
- API scoping could be better10
- Only 3 collaborators for private repos8
- Limited featureset for issue management3
- GitHub Packages does not support SNAPSHOT versions2
- Does not have a graph for showing history like git lens2
- Have to use a token for the package registry1
- No multilingual interface1
- Takes a long time to commit1
related GitHub posts
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.
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.
- Great online support2
- Perfect version control1
- Stable Platform1
- Seamless intergration with MS Office1
- Rigid, hard to add external applicaions2
- User interface. Steep learning curve, old-fashioned1
related Microsoft SharePoint posts
- Easy to use59
- Nice UI51
- Scrum friendly37
- Simple estimation28
- Slack Integration23
- Easy setup10
- Great support9
- It does the estimation better than we humans7
- Nice ios app3
- The right kind of simplicity3
- Can't seem to change the number of total points2
related Pivotal Tracker posts
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