We’ve connected Aha! with JIRA and it’s how the dev team gets tickets. We were using another tool before Aha!, but the cool thing is with how we connect it to JIRA. Now, someone outside the product management team can see everything from a high level all the projects we have going on. We have a screen we share with everyone so, for example, the sales department knows when we are going to release a new feature before it happens and it’s so easy to use.
Marketing Director - ForceManager
I honestly don’t use JIRA. It’s for the developers.
Marketing Manager - Hop
JIRA is mostly used for scrum for the dev team.
Co-founder & Chief Business Officer - Wizer
The sprint plans and everything happen in JIRA. We also use Bitbucket for our code repository. It’s from Atlassian, like JIRA, so it’s easy. We use them because the guy who uses it every day and experienced developers said we want to use JIRA. They use it everyday so I want them to be as comfortable as possible.
Founder & Managing Partner - Clever Europe
We have JIRA for payroll.
Co-founder & Co-CEO - Vinomofo
We use JIRA for everything. It’s easy to set up and the UI is great.
Co-founder & CEO - Rep The Squad
We all use JIRA. We found this new tool Aha! that complemented what JIRA has. We use that for top-level roadmapping. It is something that is not very developer-focused on bugs and features. We link it with JIRA and the two put together give us a good picture. Most work is catalogued in JIRA. We just evolved into using JIRA. We used to use Todoist or just a spreadsheet. These things don’t scale when you want to have issues categorized along multiple levels so JIRA is heavy enough, but it has lots of integrations and can handle it.
Founder & CEO - Postman
Our product team uses Basecamp and JIRA to plan out sprints and scrums. Our design, merchandising and marketing teams use either Trello or Asana. We allow teams to use the tool they want rather than standardizing it across the business. We think that each team is unique in their own way so whatever tools is most effective to help them achieve their goals is fine. We’re pretty tool agnostic and it has happened organically because people latch on to certain tools. I personally like Trello because it’s simple and easy to use with its kanban style.
Co-founder & CEO - Brosa
We use JIRA kanban boards to plan social media management, marketing calendars, and so forth. I used to be a product manager, so I’ve used every tool under the sun. JIRA is the most complete, modestly priced option, although it requires some real TLC to get set up. This causes decision paralysis for some people, but for us it’s exactly what we need. We set it up for our engineering team initially, and it’s now been rolled out to the entire team.
Co-founder & Chief Product Officer - Clark
The Atlassian suite is a hot tool set for development.
President & CEO - Full Circle Insights
Our engineers use JIRA.
Co-founder & CEO - Clearpath Robotics
Our dev team uses JIRA.
Co-founder & CEO - SalesWings
We use JIRA for development. It’s a great enterprise-focused tool--we have it connected with everything.
Co-founder & CEO - WeFind
Our development team uses JIRA.
Co-founder & CEO - MuseFind
We like JIRA for bug reporting. It connects with Slack and Zendesk. If a customer has a problem, they can report it on our website through Zendesk that then opens a ticket on JIRA.
Anne de Vries
Founder - Tubbber
We use JIRA for development.
Head of Platform - WaystoCap
We tried JIRA, but it was too complex for us--too many bells and whistles.
Founder - FastPortal
We use JIRA both for development and business. You have learn it, but once you do, it works well. It has ticketing and planning features. It supports your dev process.
Founder - Favoroute
We use JIRA for all IT-related projects and tasks.
Co-founder - Flexpat
We use JIRA for development. Nobody likes using it, except for the development team. I love the reporting on JIRA though. You can connect all these tools through Slack and automate a lot of the actions.
Founder & CEO - Zera
JIRA scaled really well with us.
Founder & CEO - Yesware
JIRA is our primary project management system for our engineering team.
Co-founder & CEO - Amper Music
JIRA has worked the best for us across design, development and product management. It has the ability to provide clarity into the product roadmap. It is also easy to use and not expensive.
CEO - Panjo
JIRA is a good development tool. Business people don’t like it, but developers love it.
Founder & CEO - Gaiku
JIRA is very powerful--we are probably using 20% of its full potential. The only issue is that the cloud version is very slow. It is a very good development tool.
Founder & CEO - API Fortress
Our engineers use JIRA for product development. They are the only ones that they can understand it. It’s pretty ugly, and the user interface is complicated.
Co-founder & CEO - Kompyte
We tried JIRA, but it’s very technical. It is a better tool for bigger companies. We wanted to have a more fluid structure.
Founder & CEO - Current
JIRA is too heavyweight for us.
Co-founder & CEO - Winnie
JIRA is really super powerful. You can define your own process. It’s not complicated to use but it is very development focused and not as user-friendly when you are not a developer. We use it mainly for product development, but we also keep a board for marketing.
Co-founder & CEO - Yalty
We use JIRA for our website development and we built our own sheets on Google Drive. We tested Asana but it didn’t make sense for us.
Founder & CEO - Sponsoo
We just started using JIRA for bug tracking.
Co-founder & CTO - Moving Analytics
We use JIRA and Confluence. The engineers are using it for documentation and bug reporting. It is catered to the engineering team so for non-engineers, it has a steeper learning curve. But once you get used to it, it has a lot to offer. It is ticket-based, great for bug reporting and tracking, and documentation for new modules/features.
Controller - Polymaze
Our engineering team uses JIRA and they are pretty happy with it.
CEO & Founder - Pendo
We use JIRA on the dev side. We were on Pivotal Tracker before. The primary benefit with JIRA is that we integrated everything with it. It is highly customizable.
CTO - Optoro
JIRA is a really good tool. We set up our own process and it is pretty fluid.
CEO & Founder - Reply
Everyone uses JIRA nowadays--it is state of the art. We also use other tools from the Atlassian suite like Confluence, Bitbucket, and HipChat. Everything is nicely integrated.
Co-founder & CTO - Price f(x)
We use JIRA for development / bug tracking.
Co-founder & CEO - Periscope
All of our company’s departments work with JIRA. At first we had an open source solution but then we moved to the full Atlassian suite. It is nice to be able to manage both product development and marketing from the same platform.
Co-founder & CTO - Musement
We use JIRA for engineering project management--it is quite powerful.
CEO - Nugit
We used JIRA because it is the project management tool we were familiar with.
CEO - Scripted
JIRA is similar to Salesforce in the sense that it gives you enough rope to hang yourself with. At the beginning we spent a lot of time on the settings level, trying to establish how we should use it. After a while, we realized that that way was not working and we had to do it all over again. We had to create documentation on how to use it. At the beginning, it can be frustrating but if you take the time to set it up according to your needs, it becomes incredibly empowering. It is so powerful and has so many options.
Co-founder & CTO - Teem
We like JIRA.
CEO - Jack Media
JIRA works great for our engineering team. It is a pretty standard product, well-ingrained in our workflow. It is not super intuitive but our engineers like it.
Founder & CEO - Embroker
JIRA is modern and has Agile functionalities, so it works well for us.
Gian Luca Petrelli
Founder & Executive Chairman - BeMyEye
I think what our employees find beneficial about JIRA is the ability to track activities across different teams. Often shipping a new product requires different teams. It works really well there and does a bunch of integration that facilitates automation in the process as well
Founder & CEO - Qardio
JIRA is a standard and it works well. I do think that their interface has become too complex and hard to use in some places.
Co-founder & CTO - Valify
JIRA is a bit complex sometimes--there are too many features. We use it for software development.
Co-founder & CEO - TravelPerk
We are pretty happy with JIRA.
Marketing Director - FreshGrade
For the engineering side of project management, we use JIRA.
Co-founder - Outbound
We use JIRA for bug tracking, backlog, customer issues and sprint planning. JIRA is great at what it does, but it is somewhat clunky and difficult to use (to some extent).
Co-founder & VP Data - Zendrive
We use JIRA internally for non-technical stuff, like marketing and sales. It’s kind of a beast.
Co-founder & CEO - ContainerShip
We use Codetree for our engineering and managing products. It’s literal project management. It’s closer to JIRA for managing engineering stuff and milestones in products. Our product engineers and managers live in Codetree more than I do. I was actually pushing JIRA, but everyone else pushed Codetree.
Founder & CEO - Allay
We love JIRA. We submit feature requests through it, which helps us avoid sending a lot of emails and arranging too many meetings. It allows us to work asynchronously, which is very valuable since half of our staff is in London.
VP Marketing - Moogsoft
Our development team uses JIRA.
Co-founder & CEO - Process Street
Our product team uses JIRA. and most of the work we’re doing is done in JIRA. Our Director of Operations had used it successfully in the past and brought it in.
Co-founder & CEO - Limelight Health
We use JIRA more for our project management than Trello. JIRA is for our development and to see our roadmap.
Founder & Chief Software Architect - PeopleVine
We’ve tried Github, Trello, and JIRA, but none of them have been a great fit. They're too technically focused, and forcing business people to use a tool built for developers makes them use the tool less, and less effectively. As a result, we don’t get as good intelligence on the status and needs of our projects. We like Basecamp and will probably end up using it soon, especially as our team grows.
Co-founder & CEO - Stylisted
We tried to implement Slack but at the end of the day, we went back to emails. We are still very small. We use JIRA to communicate about projects.
Co-founder & CEO - Articoolo
We started with JIRA because some friends recommended it. I do not have a lot of experience with other project management tools. It works fine, although there are several UX problems. Some things are done quite awkwardly. For example, if you want to add external links to your projects there is this awkward button that you click, and then you have to copy and paste your link. It feels very old school. Another example is that if you are creating a new project, you will see it on your project board only if you refresh it. Overall it works for us; it does not cost a lot and it is simple to use.
Co-founder & CEO - Articoolo
JIRA is straightforward and very powerful. With JIRA, we manage all our project management on ‘kanban’ boards. It is a pleasure to use – and integrates easily with all the other Atlassian tools.
Co-founder & CEO - YouCanBook.Me
Most of our developers use JIRA. It’s a well-known, old product. We've used JIRA for years; it is old school. There is no communication except for comments. It is a bit cumbersome because we have long running conversations. With JIRA, you can make comments and assign tasks.
Co-founder & COO - TradingView
We consolidated everything in JIRA. We felt it was easier to have everything integrated.
Co-founder & Chief Architect - SwiftIQ
We used Asana, but we switched to JIRA. All our dev process management revolves around JIRA.
Co-founder & Chief Architect - SwiftIQ
JIRA has a steep learning curve but is really customizable. The UI could be better.
Co-founder & Chief Product Architect - Koding
My developers suggested we use JIRA, so we went with it. Our entire team uses it; from developers to marketing and sales. It’s a great tool.
Co-founder & CEO - Concord
We use JIRA, and it integrates well, and is easy for the developers to use. We’re happy with it.
Co-founder & CEO - PowerToFly
I’m a product manager, so obviously, JIRA is my power tool. I tried Asana before, and I didn’t like it at all. JIRA makes sense, and feels like it was built by people who do this job all the time. There are a lot of options to manage our processes and team with it, without being intrusive.
Founder & CEO - Peerlyst, Inc.
The engineering team uses JIRA. They’re the only people managing projects at the moment, so pretty much everything is managed in there.
Founder & CEO - Gigwell
JIRA is okay. The development team was used to it, so we went with it. We don’t use every aspect of the tool yet, but we hope we will be able to in the near future. Hopefully we’ll be able to automate a lot of it as well. We use JIRA to create sprints. It’s not the best tool for sprints, but it works. We also use JIRA for customer service issues. We use Zendesk, but when an issue is reported, it gets reported to JIRA directly.
Founder & CEO - TechnoRides
JIRA started with our engineering team, and now our marketing and sales teams use it. It’s definitely built by engineers, for engineers, so a lot of the UI and UX doesn't make the most sense to non-engineers. I’ve used Asana in the past which has a better UI/UX, but it’s not as robust from an engineering perspective. We wanted to make sure our engineering team had the tools they needed to develop a great product.
Co-founder & CEO - LeafLink
We use JIRA, with the Wizeline plugin. JIRA is a phenomenal issue-tracking tool. It’s very good for giving you a snapshot of the here and now.
Founder & CEO - Wizeline
We tried to integrate everyone into Podio first, but then migrated from Podio because the developers wanted to use JIRA. We all use JIRA now, and it’s brilliant. The only downside is their notification system; it feels like it should’ve been upgraded years ago.
Founder & CEO - SprinkleBit
We use a lot of JIRA. Our services, product, and engineering teams all use it.
VP Marketing - Extole
JIRA is used more for our product and engineering workflows. It has a very bloated feature set, in my opinion. We use it and get by with it, but I wouldn’t recommend it for a small agile company. For bigger companies that have lots of people, and need a lot of cross-company communication, it might be an effective solution.
Co-founder - FullContact
We host internal docs on JIRA.
Co-founder & CEO - AdStage
We use JIRA for engineering projects.
Co-founder & CEO - AdStage
The engineering team uses JIRA for sprint planning. We used Asana in the past, but organizing it took a lot more time than we had to spare. With JIRA and Trello, you put a card in, you tailor it to what you want it to be, and then you’re good to go. We like the simplicity of both JIRA and Trello.
Marketing Manager - Shippo
On the engineering side we use JIRA. It’s good at what it does.
Head of Marketing - Pipedrive
We use JIRA for development. We like it; it’s better than Trello for tracking tasks and getting them completed. Overall, it’s a good tool.
Founder & CEO - Brick & Portal
We use JIRA for managing projects, and we like it. It’s very technical in nature, and definitely not flashy. It’s not the most beautiful platform, but the bottom line is that it offers everything other tools offer, and more. If you can ignore the aesthetics, which we have, it’s a formidable tool. We’ve also integrated JIRA with Zendesk, which has been great for our team. We use JIRA’s agile dashboard to manage our sprints and provide our team with a current scrum view.
Founder & CEO - Shoppimon
We use Confluence for planning, and it’s fine. As a wiki, it’s pretty good, but there are times when it’d be a lot faster to just make a Google Doc or Google Sheet and use that as the primary database for collaboration. What I really want is to be able to create a Google Doc or Google Sheet and have that tie in with Confluence. The Google Docs integration is not terrible, but it’s far from great. What I really liked in Confluence in the past was the ability to create a table in Confluence with a list of issues. You could go into a Confluence table and type in your 10 issues, for example, and then push a button and that would turn into 10 issues in JIRA. And anytime anything was changed in JIRA, you would see it on the Confluence page. That integration was very powerful, but it’s been broken for at least 2 months at this point, and they don’t seem very motivated to fix it. This might be a single bug that is only important to me, but I do see a lot of people complaining about it online, and it boggles the mind trying to figure out why they’re not focusing on fixing this issue.
Co-founder - BuzzStream
We use JIRA for issue tracking, and we love it. We switched to JIRA from FogBugz. We used FogBugz for the first three years of the business and we liked it a lot at first. Over time though, it became clear that it wasn’t moving forward; it was slow and it lacked some very basic things (like a scrum board). JIRA is much more fully-featured. We love the scrum board; it’s fantastic. And we just find JIRA really easy to use. It’s also fast, and gets us what we need. The only downside with JIRA is that setting it up is a pain, and you have to get it right. If you get the setup right, it’s fantastic. But if you don’t, you’ll be annoyed with it.
Co-founder - BuzzStream
We used JIRA in the past, but their UI was very complicated and not intuitive at all, so we dropped it.
Co-founder & CEO - Veed.Me
We use JIRA for bug tracking and tech products. JIRA is fine, but it’s a little bit like HubSpot, where configuration can be pretty complex.
Founder & CEO - Justworks
We enjoy using JIRA a lot. I’ve been using JIRA for four years, and I think it’s the best tool for project management. Another plus is that it’s also quite cheap for small teams.
Co-founder - Chrobrus
JIRA is very good. We use it specifically for the development team. We can easily tie all tickets to a sprint, as we use the agile development method.
Co-founder - Simple Texting
I like that JIRA is more detailed than Trello. But JIRA isn’t appealing to look at, which is a bit of a turnoff. And for us, working on an app, JIRA is not conducive for posting screenshots with notes, such as, “Change UX and UI here. This button needs to move in the app.” JIRA is not as useful for that, but on the other hand, it has many more layers and is a more sophisticated tool than Trello, but not as user-friendly. With all of these tools, it really depends on the user. I wish JIRA had a more visually compelling and cleaner look to it, but tech people seem to really like it. It was one of our tech team members that suggested using JIRA in the first place. I feel that when a tool is more complicated, there is more potential to get lost in that tool.
Co-founder - GoKid
Given our past experience at Gilt, we decided to use a familiar tool. JIRA is used across our organization – tracking issues, managing weekly sprints, producing marketing assets, and prioritizing product photo shoots.
Chief Design Officer & Co-founder - Zola
Our dev/engineering team has gone really deep with JIRA. But our customer success and marketing teams never really picked it up, despite some internal efforts to have that happen.
VP of Marketing - Unbounce
All of our teams use JIRA. We’ve very satisfied with it.
Co-founder & President - Work Market
As far as JIRA, the development team knows it better than I do, but it's been good with complex dependencies and really technical factors.
Founder - SenseHealth
Our development team loves JIRA. We tried Asana for other work streams, but it didn't catch on.
President & CEO - Selectable Media
For more technical, large-scale or multi-point of contact projects, JIRA works great. It’s easy to access and very self-explanatory, but the costs quickly jump between services. For simple project management, the cost is quite low, but to allow for a scrum or agile method, the costs double. To then integrate usage between an ops/service team and a technical team, it triples.
Director of Operations - Inxent, Inc.
We had also been using Trello for product development, though we just recently added JIRA for our engineers. More substantive and has more integration capabilities than Trello, though Trello is much easier for early-stage startups. With JIRA, there's some upfront work that needs to happen before you can use it effectively--you need to know what you're doing and what you want from the tool to set up JIRA well.
Co-founder & CEO - sli.do
Our dev team uses JIRA, and that is just ridiculously good for remote development. Some of our developers are in Moscow, and JIRA was by far the best at keeping everyone on the same page.
Co-founder & President - ALICE
... JIRA is a great collaboration tool!
Co-founder & CEO - SponsorHub
JIRA is painful to customize, but once that part is done, it’s very powerful. Plus, it scales for larger teams.
Co-founder - Monaeo
We use JIRA for scheduled project management, and we use it in a more structured way to move forward with the product. We pay for JIRA.
Founder & CEO - Pollfish
JIRA is so comprehensive, and our engineering team was already familiar with it.
Co-founder & CEO - Ampush
JIRA itself is not the most user-friendly, but it is very customizable, and it's one of the most established product management platforms. Used in conjunction with Instabug, it’s great for bug tracking.
CEO - Truffle
On the development side, we're heavily dependent on JIRA. We use this as a central hub for ticketing, and use it to manage our software development and QA processes.
COO - Citia
JIRA is a begrudging choice because the tool has so many drawbacks: It’s overly complex, slow, has confusing terminology, and mind-boggling frustrating design choices. But when wielded effectively, its level of customizability allows you to simplify the screens and customize the workflow for each team to make the tool match the process. This is the greatest aim of any project organization tool. We integrate JIRA with Github, Zendesk and Slack, so that tickets are our universal increments of development.
Founder & CEO - Layer
We use JIRA on the tech side, and our team seems to like it for prioritizing bugs, fixes, etc. I don't like that it doesn't let you see the website or back-end portal that you're testing and easily click on the specific area you'd like to comment on. In JIRA, you have to start every ticket by describing the place on your site that you're referring to.
Co-founder & CEO - Manicube
JIRA is our main project development tool, helping us track issues and project progress. It is a tool that requires heavy customization and if not properly managed by QA and Project Management can become overwhelming. We use it to build test cases and requirements. It has received good reviews to date.
Founder & CEO - Kargo
We've analyzed and compared a bunch of tools hoping to find something free. I think we spent three weeks comparing tools nonstop. We looked at everything out there--Pipedrive, Asana, Basecamp, Sprintly, Pivotal Tracker, and a few more--and each of them was missing something because it’s hard (read expensive) to build a total solution for project management and offer it for free. We ended up using JIRA, which it isn’t free, but it’s affordable. We knew that we would grow really fast, so that was part of the decision to not go with one of the free ones ... GitHub integrates really well with JIRA. We also got an add-on for JIRA, called Capture, a screenshot feature that makes it really easy for non-tech people to submit bugs.
Co-founder Stage: Seed - Sailo
It sucks, but there's nothing better out there. It's super complex, but the alternatives are all too simplistic. I think it's just a complicated problem in general. There might be better solutions out there, but I just don't know them. It feels like the complexity gets in the way of the workflow.
Co-founder & CTO - Concord Systems
23%Stacklist Startups Are Using JIRA
JIRA is the powerhouse of project management tools, boasting a flexible platform that’s geared specifically toward developers. While JIRA can handle a wide variety of tasks, including project planning, tracking and detailed release reporting, it has a decidedly technical bent. It’s not uncommon for companies to use JIRA only for their engineering teams, while all other teams use a lighter-weight tool like Trello or Asana.
Because JIRA is so complex, smaller teams with simpler organizational needs tend to shy away from it in favor of something easier to use. As such, JIRA is disproportionately favored by larger series A and B companies that have plenty of employees and a more involved development process.
JIRA has three packages, depending on your needs: a “for projects” package that handles issue tracking only; a “for development” package that handles both issue tracking and project management; and a “for service desk” package that also handles service requests. Like most project management tools, you can purchase a monthly subscription to JIRA that increases in cost depending on the number of users (the cheapest monthly package starts at $10 per month for 10 users), or you can purchase your own server. The latter option starts at $10 for 10 users, but jumps quickly to $1,200 as soon as you exceed 10 users; at that point, the payments shift from monthly to annual and the you (the user) are responsible for server management.
Visit the website: https://www.atlassian.com/software/jira