Jira Core Reviews

Derwin V.Enterprise(> 1000 emp.)

5.0

Jira is one of the most intuitive services ever developed. The easier implementation on your daily basis is amazing. When you use it every day, you will notice how ease you can interact with it and how great it integrates with other services. The features are amazing even though those features depends on the each business. I use every day and I rarely have had any issues. The customer support is great and it works perfectly fine whenever you have to report anything. Review collected by and hosted on G2.com.

Marianela F.Consulting - Water treatment - Environmental management

4.5

Jira allows us to customize each environment to focus on the activities that interest us most and offers the project manager a global screen of the execution, which makes it easier to follow the critical path and ensure that the times are the most convenient for execution of the project. Review collected by and hosted on G2.com.

Rohit G.Programming Analyst

4.5

I frequently use it's core feature of issues tracking as it makes issue tracking efficiently easy. Review collected by and hosted on G2.com.

Verified User in Information Technology and ServicesMid-Market(51-1000 emp.)

0.0

It is complicated, has far too many features that are hard to navigate, it's expensive so not all our team has access and the formatting sucks Review collected by and hosted on G2.com.

Verified User in Information Technology and ServicesSmall-Business(50 or fewer emp.)

0.0

, , . Review collected by and hosted on G2.com.

Verified User in Information Technology and ServicesSmall-Business(50 or fewer emp.)

0.0

Very unintuitive to use, as a software developer I can figure out applications pretty easily but there is no hope for JIRA. Page loads are kinda slow but bearable. Review collected by and hosted on G2.com.

Zie Mamadou C.Computer Software

5.0

Jira est un excellent outil de gestion de projet, du point de vu de sa popularit et aussi d'tre pouvoir utiliser dans multi domaines

Anonymous ReviewerManagement Consulting

5.0

Jira helps team discover agile foundations with the guide of a scrum master or project leader. The sprints provide guardrails to teams take smaller chunks of work. Jira provides a centralized location to work in and can reduce the amount of communication gaps.

Emiliano L.Law Practice

5.0

Dispone de una interface bastante intuitiva que cualquier trabajador comprende rpidamente.

Verified UserEngineer

10.0

Atalassian JIRA is used in my organization in almost all phases of software development, right from the requirement analysis to deployment. Any requirement, enhancement is logged into JIRA and assigned to a requirement analyst, then it is assigned to a developer, next to QA Testing team. Each bug/defect is also logged using JIRA. It is also used for deployment where in a Sytem Engineering ticket is raised for QA, UAT, Prod deployment which is follows various approval cycles before it is deployed. So to summarize, JIRA is used by Analyst, Developer, QA, Release Engineer, Support team, Manager, and each person who is responsible for quality and valued Software.
First of all, it keeps a log of each and everything you do for a software, and it takes the responsibility of creating a process for an organization. It keeps track of all the bugs, completed, pending which gives a proper estimate of allocated Vs completed work and helps you to focus on the required area. Since JIRA has a feature to log a bug with a proper workaround, It helps a new member to go though all the open bugs in the system and find out what workaround to be applied if similar problem occurs.

Verified UserDirector

10.0

Atlassian JIRA is being used by two departments within our company. The more obvious is our tech team, which uses it for bug tracking across our web/app development projects. My team has "adopted" JIRA as a way to task manage our web production and processing. We receive video assets, imagery and metadata to publish to multiple web sites. Tracking progress and assigning tasks associated with this ongoing workflow has made JIRA an invaluable tool for us. We complete hundreds of titles per month, and before JIRA tried to task manage in Google Docs.
E-mail notifications; the fact that reporters and watchers can stay in the loop via "push" and not "pull" is amazing The fact that tickets are of permanent record; they can be closed but not deleted The ability to clone JIRA tickets is very helpful when we are building out batches from the same partner or episodic content The ability to link tickets helps us keep work batches connected Labels make it so easy to push-to-filter tickets Due dates help us to manage deadlines

Michael TrujilloQA Manager

10.0

We use it in our entire organization. It addresses the needs of multiple departments with use of multiple projects along with the handling of defects and upcoming projects.
Error Handling Swimlanes Kanban

Verified UserAdministrator

3.0

It’s being used all across our organization. It addresses IT related issues and is a direct line to assist all workers.
They don’t always know the real issue and spend too much time figuring out the wrong solution Sometimes they pass around the issue for days. They need to understand all software programs well. Multiple attempts needed to bypass admin access

Verified UserConsultant

4.0

JIRA was used to document differences between a desired specification and a delivered prototype. The organization being small, it was used by everyone. It was intended to be a single tool to characterize issue reports, compile bugs, author work orders & track progress for a web-based application tracking various aspects of building management & efficiencies.
JIRA is part of a silo with Atlassian's other tools, like Confluence wiki. Just as Microsoft tools integrate tightly with its Sharepoint knowledge base (it's not a "wiki" in my opinion), Atlassian's form a stack that essentially requires one to use Confluence. Meanwhile if you are using the far more common & supported MediaWiki, you will find that for various reasons it is wiser to use Phabricator, the Facebook/WikiMediaFoundation bug reporting tool (competitor to JIRA) since the largest users of PHP-based mediawiki are also using that, and integrate them more over time. If JIRA wishes to compete for users who are relying on SharePoint & MediaWiki, who very much outnumber Confluence users, it will have to support those knowledge management / CMS / wiki systems as peers, and will have to restrict the degree to which it favors Confluence else it will be too great a business risk to rely on JIRA when using a non-Atlassian CMS or wiki. JIRA does not provide much direct support for support-driven development (SDD); that is, when one is specifying a new product entirely, with desired (not real yet) fictional features, JIRA would have some trouble characterizing this correctly. Yet for SDD it's critical to be able to represent a specification of desired behavior even when there is no running code that attempts to implement it, else there will always be a gap between a specifying tool and a support tool. JIRA developers would have to make a conscious decision to support "revision 0" of software; that is, its specification without any working artifact, and with only proposed URIs or command verbs, keeping these mutable so that potential support problems were found in the specification stage, and there was NO gap between tools used for revision 0 versus revision 0.1 to 0.9 to 1.0, only a difference in audience. Mobile & responsive support is weak - when a problem is reported it should be relatively easy to filter who gets which reports, and those should be sent through confidential means like XMPP or Signal, rather than relying on proprietary services such as social media (major security problem).

Kyle KochtanTechnical Lead

5.0

JIRA is being currently utilized as a second tier ticketing and workflow management system. Our users create a ticket in our regular ticketing system for an enhancement and such. Once it has been approved a ticket and sub tasks with all the detail are input into JIRA and tracked. We then use JIRA in our weekly meetings to give updates and such.
The UI In JIRA is not very intuitive, they have comingled products and navigation is difficult at times JIRA can be annoying with the number of email notifications it shoots out JIRA's security model is overly complex and can lead to issues

Janosch F.Human Resources Consultant

5.0

Jira surprised me as coming across simple yet being incredibly powerful and versatile. It is a full blown Ticket and workflow management tool and it might be too much for small or personal projects. However, not being required to change the ticket system when the company or the team scales or are faced with types of tasks you did not expect is simply fantastic. Keeping software simple, easy to use yet increase its versatility and power is a virtue and Jira is build upon this virtue with care and vision
Jira is clean and it is simple yet powerful. You can use it for your basic ticket workflows from the get go and expand as you grow or the tasks you wisch to cover branch out. It is easy to customize the ticket views to contain the information you want to use and avoid cluttering. The Workflow editor is one of the most powerful I came across in all my professional career. It might not seem so much of an importance but believe me, when your business grows unexpected necessities will arise and you will suddenly be required to track tasks you never though about. Jira will have you covered and allow you to add different task types which traverse task-type specific phases and have corresponding stati. Also you have all the world of notification and responsibility tracking ping-pong covered as you go. Two further things are woth mentioning: First the Atlassian World (the Wiki Confluence and build system Bamboo and many other products) integrate flawlessly and it actually really makes using them fun. Jira is one of the tools, that make you smile when you are required to use it no matter the task to track, its jus smooth, convenient and above and beyond provides a rich ecosystem for free and commercial plugins even for rather exotic use cases. Also, the license Model behind it scales fantastically. When we introduced it we were a small company with 8 people (we are now going strong towards the 200) and it was critical to keep cost for our tools reasonable. Jira got us covered.
When we scaled, the License was not as flexible in higher user tiers as it was in the lower ones. Also once upon a time an update went wrong and we had to invest a bucketload of time and brain power to get everything back up to speed. We did run jira on premise and hat some custom plugins so there might be some of the tripwires: In case you use plugins they must be available in the version you wish to upgrade to and this might require some research prior to updates. Also, you can make a science out of the workflow and notification configuration. In case it is not documented well when you do it it might get you into trouble.

Verified Reviewer

4.0

I love using Jira as I can configure it as per my project's needs and I highly recommend this tool if your team is following 'Agile Development' process.
I have found JIRA to be much more flexible (for workflow management) as compared to Microsoft DevOps.
I have been using Jira from last 5+ years now for Backlog management, Requirements management, Bug tracking and creating Dashboards for project review meetings with leadership. It's extremely flexible tool where you can configure your own workflows and customize it as per your project's needs. It's my go-to Agile project management tool (especially for Scrum). It's so easy to create and manage user stories, bugs, technical tasks etc. You can tag your user stories as per Epics and Features, you can also add labels to each ticket. You can track the status of any ticket and also see the bandwidth allocation of various teams. In JIRA, you can add advanced search filters to view only those user stories that has particular combination of fields (like specific assignee, status, epic name etc.). Moreover, JIRA Dashboard provides a bird's eye view of the overall project status which gives the real time visibility to you and the leadership team. The UI is very clean and simple and it makes Agile Development very productive, once you get the hang of it. Plus, it's very well integrated with many popular apps like Google workplace, workday, slack etc. But there is definitely a steep learning curve with Jira. The success of this product largely depends on how your management/leadership standardize various processes and workflows within Jira.
Jira doesn't allow you to add multiple assignee on one user story, and this becomes a concern when multiple developers are working on one story. Also, it's hard to get support from Atlassian when you are facing some technical issues. Additionally, in my experience, I have found that as Jira provides great level of customization, it can become really messy, if multiple management styles are involved during project planning phase. The workflows can get overly complicated and as a Product Owner, you find yourself stuck in updating the ticket statuses all day long.

Enrique R.CTO & CIO

4.0

As I already mentioned in the example of use in the Pros section, from the simplest project (a shopping list), to the most complex, the integration of several work teams from different areas and several very diverse projects, You need software that makes work, communication and organization easier.Jira offers us that, simplifying the management, planning and management of issues, without Jira, order becomes chaos.
It is expensive to maintain and you never get the ease of use and tools of software of this quality.
I will give an example of how I used it on one occasion and the advantages of having had this software.I was hired by a digital marketing company to improve proprietary applications, internal APIs, creation and migration of landing pages made in WP for our clients, migration of PHP applications to Python, server management, diversity of containers... The DevOps who was doing all that work left the company.An external audit was hired that provided workers spread all over the world, Spain, India, Latam...So we find ourselves with a lot of work, from very different areas, work environments and projects of all kinds and just one person to manage everything.With Jira we all worked under the same environment to organize tasks, but above all incidents and bugs, and with the need to manage the priorities of each new element that entered our work boards.At a glance, I could assign tasks, review code, refactor or modify it, and upload it to the test servers. Review the tickets, with screenshots of the errors or the new results that should be obtained. Keep in touch with everyone from one place and also receive all feedback in Jira.It was months of hard work, without Jira it would have been impossible to manage it.
Despite having Jira with everything necessary for software development, sometimes it becomes more complex and less visual than if we accompany it with some extras, also from Atlassian. So it is easier for some boards or planning to use Trello, GitHub or Bitbucket for continuous integration, Sourcetree to make the different branches and versions more visual, Composer for team collaboration...

Verified Reviewer

4.0

It took time to get buy-in from the entire IT department to fully utilize JIRA. However, now that the whole department is all-in, JIRA has truly made our work effort much easier. We now have internal business partners who utilize JIRA to review work status, set priorities, and create new tickets when issues/upgrades present themselves. With an organization our size, I can't imagine not utilizing something like JIRA...not sure how we did it all in the past.
The best part about JIRA is the ability to keep track of all work being done via tickets. I love that JIRA works for all kinds of styles of work. We work within an Agile environment, with some teams using Scrum and other teams using Kanban. No matter how the team is structured, they utilize JIRA tickets. This is great because there is a single repository for all work being done and we can easily search for tickets across all the different teams. The use of Epics vs. Stories is very easy too. We can keep track of what tickets belong to which effort with ease and show the progress of work through the tickets. We can also easily maintain a backlog of tickets. If two separate people submit a similar ticket (or at least two tickets that reference the same work effort), we can combine those tickets easily so that we aren't feeling overwhelmed with more tickets than actual work.
The biggest debate among our team members is when it is necessary to create a ticket. JIRA has created a culture of needing to log every little thing, even if it takes just a moment to complete the work. Sometimes, it takes longer to create the ticket than to complete the task at hand. That tells me there is too much reliance on JIRA to report work completed. It causes some in management to show that their department is succeeding simply by the number of tickets completed. But the tickets don't tell the whole story, especially because there isn't a time component to those tickets being completed.

Brian J.Crew Member

4.0

We are able to use JIRA to create, collaborate, test and deploy promos and emails for my company. I am able to see conversations and other notes from people I don't normally interact with, which can be really helpful in understanding issues that arise or other notes that may have been left out of conversation elsewhere. It's a great tool for us.
I work for a large clothing retailer that often runs promotional coupons and sends out emails to customers. JIRA houses all of the collaboration for our company in creating and testing these promos and emails. What I like is that everyone, from the communications team to the Quality Assurance Team to the IT troubleshooting team can be in one place to resolve issues quickly. I love that there is the ability to tag other users and quickly get attention to issues that need a fast turnaround (emails and promos are often made within 48 hours from creation to launch). I also really like attaching 'sub-tasks' to a main project; This keeps organization a priority without having to search for every related task associated with a project. Related to this is the ability to attach documents right to any project/task for easy download. You can save searches and filters to your home page. For example, I have a filter for viewing only email projects, and another for promotional information. Once you get results, you can sort by title, date updated and a few other categories.
At first glance, the layout is a bit overwhelming. You have a giant list of projects, and the search doesn't always bring up what you are looking for. It takes a bit of time to learn how to navigate. I would probably like to see 'tags,' or additional ways to categorize a project so that you can search for it through a few more parameters. For my needs, this isn't too important because of the short lifespan of emails and promos. But I could see other applications needing something like that.

Kristin L.Technical Writer

4.0

Tracking, organization
I am a technical writer who used JIRA as my first introduction into working in a close-knit, agile programming environment. I really appreciated the clean design, multiple ways to accomplish tasks, and logical visual representations of concepts. Is something assigned to you? It has your face on it. We had several development teams working in tandem and JIRA allowed for each team to structure their sprints according to their own preferences (some had more traditional set up and others used kanban). As time went on we were able to add more projects to JIRA, after transitioning off of ClearQuest for our baseline fixes, and while there is certainly a learning curve getting established programmers who have used one system of tracking for 10+ years converted to using JIRA, most everyone was able to transition and feel comfortable within a few weeks. Speaking as a non-programmer, I found JIRA to be incredibly useful and easy. Tracking writing and editing projects through development didn't require any specific setup or features and it was all around a great tool.
While it was great that every project could be tracked from our one JIRA site for my relatively small (30ish people) development team, any time fields needed to be added for one specific team to track something for stories or bugs, it was there for everyone. This led to having rather cluttered add screens that meant for a good deal of scrolling. I know some of this was surely user error, but having a bit more control would be nice. Also, the search function occasionally would just... not work. At all. As adorable as the sad faced little magnifying glass was when this happened, it would be very frustrating to lose functionality without warning. Being browser-based always makes for risk and some days would just be constant checking of if JIRA was up again so untracked progress didn't fall through the cracks.

ChrisRiley

2.0

We are using Jira only because all of our developers were familiar with it. The price is right, and it does the job. That said. Their UX is constantly getting worse. Their packages are confusing. And there are some really strange things. For example why would a link in a ticket open in the same window? It should always open in a new window of course I do not want to close the ticket to view a link. This small issue alone has wasted a lot of time, and created frustration during standups. O...

j4n

1.0

I am using Jira, Confluence and their newest addition Trello for some years now and I would like my time back. As others posted here previously: the pricing is ok as long as you dont really use it. and the UX is non existant or even offensively stupid, e.g. create a new user account and send the link to a customer. In the world of Atlassian this now requires the user to login via Desktop to initialise the projects that were assigned to the user. But if you login via mobile there is no project ...

Entrepreneur_of_century

3.0

Not a bad task manager. Don't really like the UI, not clean or straightforward. And pricing could be lower. Rest is fine. Pretty much recommended.

beachlife_sarah89

5.0

It's a powerhouse of a product and a must have for any good product manager. Highly recommend using it. Has a slight learning curve, however.

muqos

1.0

It's the industry standart but it is not that good