Jira Reviews

Jira is an immensely powerful issue management tool. It's JQL language provides ultimate flexibility to satisfy the needs of all roles on a product/project team. It's easy to use (if agile concepts are familiar to you and semi-intuitive if they're not), easy to deploy (especially if you're using Jira Cloud) and easy to integrate with.

The pricing model for add-ons. You could have a 100 users registered to your Jira instance, have an add-on that is used by a small handful of power users, and still be paying a license fee for all 100 users. Very annoying!

Jira has a weekly release schedule which means the product is always being improved or changed. This is usually a good thing, although I will admit that sometimes it isn't. Jira is also incredibly functional for a broad range of use cases, from managing a simple to-do list, team task tracking, process automation, to software development. They do a good job of making it user friendly and easy to onboard, especially since they started making drastic UI improvements a little over a year ago.

A consequence of being capable of so much is that it can be hard to configure initially. More specifically, which features you need and which can be disabled. There are a lot of great features but some just complicate the workflow, and it usually takes time to figure this out.

JIRA is an industry standard tool, due to this it's very well known and a colloquial metaphor for "tickets" in and of itself. JIRA is able to handle monolithic projects and the many related projects with regard to them.
JIRA is very good at allowing and automatically building self-referencing tickets within it's comments and ticket parts, if you put a ticket title into a ticket it will automatically reference the actual ticket with a link. It is also very good at adding to existing tickets with related tasks, sub-tasks, and prioritization. JIRA also is considered in almost every third party tool with a massive volume of software that offers "JIRA plugins" considering it's high stature with the IT community.

JIRA is "the tool" but it's not "a good tool" for every project and company size. JIRA is like other commercial grade products that just aren't designed for simple day to day use. While it opens up nicely and begins to make tons of sense in larger projects, larger organizations, and larger teams it often doesn't show the same beauty with simple projects and day to day ticket tracking.

Additionally, the JQL language is ridiculous follows in the foot steps of many other proprietary languages that are only great for constant users of JIRA. While that's the implied scenario because as mentioned JIRA is "the tool" it's not always the case. When my day is split 20 ways, I have little time to sit down and do more than plug in a JIRA ticket number to get to the issue to investigate, review, get sign off on a fix, and apply.

JIRA is also having what appears to be a lot of difficulties this year staying online with their new data center providers. I don't remember ever having these issues prior to their most recent move.

1. Issue Tracking: Jira Software allow my team to create and track issues or tasks.2. Support Agile Methodologies: Jira Software supports Agile methodologies. It provides boards to visualize and manage work, backlogs to prioritize tasks, and sprints to plan and track iterative development cycles.3. Integration: Jira Software integrates with various tools and services commonly used in software development, such as source code repositories (e.g., GitHub, Bitbucket)These integrations enhance collaboration and streamline development processes.4. Reporting and Analytics: Jira Software provides built-in reports and metrics, and that helped me to track project progress, team performance, and issue resolution.5. Customizable Dashboards: Jira Software helped me by creating personalized dashboards to monitor key project metrics, track assigned issues, and view activity streams.

1. Complexity for beginners: Jira Software can be difficult for users who are new to the platform or project management in general. The extensive customization options and complex configuration settings may require a learning curve and additional training for some users to fully leverage its capabilities.2. Expensive: While Jira Software offers a free tier for small teams, the pricing can be quite steep as the team size and feature requirements increase. This can make it less accessible for small or budget-constrained organizations, especially when considering the additional costs of integrations and add-ons.

the deployment was easy and you don't need any special skills to do

user interface is not as easy as it should be, I feel they need improvement on the front end side of the app

Of course there's a little confirmational bias in any review of a product already acquired, but implementing it really was a thoughtful decision. Over the last few years, this product has really matured. When we started with it as an immature FOSS offering, it wasn't really enterprise-class. We were motivated by cost initially, but Atlassian has really grown it. Now with external directory integration, tiered hosting offerings, MSP-level features, and significant customization available, I can't think of another product that beats the value proposition. My most favorite feature? The return on investment. We use this to manage service desk interactions with more than 25 MSP clients, and have never been let down. It costs us less than weekly staff meeting pizza to operate and integration with other Atlassian products is superb.

Much of the branding customizations fall flat. Inability to resize or edit logos, the prominently featured plugs for Atlassian throughout the UI, and clunky DNS-tricks requires to redirect customer portal URLs to MSP's domain.

Extensibility. Jira really can be all things to all users. There are so many business workflow processes that we have implemented and all in Jira: advanced software development, workflows for processing contracts and invoices, and support work with incidents and service requests with approvals.

Lastly, with the large dev community and a large pool of app add-ons, we are confident we could extend Jira to be what we need it to be.

If you don't understand the principles of Agile software development, there will be parts of using Jira that will be foreign to you and will likely go unused.

There is a steep learning curve on the administration-side. With so many functions and features, it can be difficult to know all of your options. The "schemes" that power the project administration can also make it difficult to troubleshoot your setup.

Easy to create Agile dashboards to track bugs in different development life cycle. We can also extract informations regarding the user specific tickets created and worked for any period of time. Also we can attache documents to gives an entire idea about the the bugs and time tracker in comment section provides how much time it takes to fix the bugs. In the software industry JIRA is one of the widely used Bug tracking platform. The idea of classification of tickets like EPIC,Task are very useful to identify the work load needed for that ticket.

Need exact date and time of the ticket creation and comments when the ticket gets older, right now it describes like the ticket is "created more two weeks ago". JIRA also needs to integration with CICD tools for more information regarding the bug tracking and fixing. JIRA should provide a dashboard for each user how much time he worked on a ticket to track the overall work time and also it will be very easy for the Administrator also.

The task tracking and overall reporting are pretty solid. If configured properly, you will not miss on any updates and can proactively resolve blockers.

The configuration. They are very complicated and you cannot expect a new user to get it right and that's why there are dedicate people who set up this. We did it on our own and it took us a couple of months to get things right.

Everything ! the software is very powerful, it has a lot of options and features:
- Scrum, Agility and flexibility of changing flows.
- Security setup for every type of users.
- A lot of features ( no way to compare it with any other software i know )
- Very simple to use
- Sprints support..
- High Availability.
- Awesome Designs ( old and new ).
And so many other things i love about JIRA

I wish the cost was a little more less for small sized companies.

Jira is very flexible and can be used for different use cases, eg: project management, issue tracker, road maps etc.
It is quite easy to configure compared to other generic project management tools.

The transition from old user interface to new one, it is very confusing, the UI is not consistent when we visit URLs from email notifications.
Compared to other generic tools, Jira is quite easy but still it is not easy to setup, it takes quite a few days to configure the system as per needs. It would be great if there were boilerplate templates.

Jira provides a ton of features in terms of project planning, the ability to create a hierarchy of epics, and feature > delivery > story, which is a great feature to track deliverables in a release. It provides sufficient options to write detailed stories, add functional workflows, excel data sets, etc. Helps in Issue and bug tracking during production support, UAT phase, and QA testing. A great collaboration platform, due to the ability to write comments, notifications, tag required personnel, and seamless integration with other tools such as Outlook and Confluence.Log efforts and Tempo (dashboard to track daily efforts) is an amazing tool for productivity enhancements.

There are a few limitations of JIRA as well - - The search engine of JIRA doesn't always fetch the correct results despite using the correct keywords, it's not as smart as an AI-powered engine or Google. Also, the Smart Query feature is not that useful, many times basic search work well.- Doesn't have the templates to write detailed documents such as FSD or a design document, not a very good knowledge management tool.

Flexibility in workflows and tracking separate projects and sub-projects in the same system.

Ease of creating multiple tickets as well as placing them into different projects without having to be in the projects portal.

Creating reports to review metrics is relatively easy, it was useful in an integrated project to review estimated times reported in previous sprints to project development times for other projects.

The flexibility of how tickets look and editable fields as well as workflows to tailor to the team and/or project being worked on.

The bad part of Jira's flexibility is that settings are all over the place and you typically need to refer to Jira's knowledge base on how to configure custom settings whether it is for fields inside of tickets, workflow settings and automations, and many other settings.

The standard Jira end user interface is not exactly user friendly and some things may not make sense depending on the team using it such as a ticket being in a closed state however the resolution state has separate "states" such as do, don't do which is more used by software development teams.

Jira typically requires a lot of customization when setting up new projects either for project managers, agile software development teams, or integrated project teams. As an administrator this can be difficult to convey to my end users who want to track their projects in Jira. This is where you need to have great communication with your end users to be able to setup and tailor the Jira project to their needs and improve the overall Jira experience.

Jira is highly customisable, and also has plugins. It allows you to monitor your projects and provided granulated access to individuals. You (or your admin) can set roles for the project and associates those roles to certain activities and then associate the roles even further to individuals.

You can organize your tickets in sprints and releases as well as monitor workload and task assignment to your team during sprints (or whatever other form of software delivery you wish to choose).

Pricing model. Currently, you have a choice of server vs cloud setup. If you have a team that can maintain the server instance, I'd recommend going to server because you have a lot more plugins you can use on server and you can set it up the way you want. The best thing is the licenses are a one-time cost, as opposed to lower, but monthly and forever costs on the cloud portion.

The other thing that is to be considered is that the plugins you choose need to have the same level of range for hte user count. i.e if your jira is for 101-250 users, all your plugins will need a license level of the same range, i.e 101-250 users. Something to consider if you are thinking about moving to Jira.

Jira is an incredibly large and flexible tool to the point that you can virtually have any kind of project - software or not - managed inside it. But though it is large, it is also relatively simple to being with and can accommodate simple workflows even for smaller teams, with some neat ready-to-go templates.
But its abiity to grow into a platform that can support a large corporation is amazing. Scalability is definitely their main power.
Jira also bennefits from a very large marketplace of plugins that can bring more functionality and fit the granular specificities of each company or project.
It also has a very cheap pricing for smaller teams.

Some basic functionality if just not there, which is rather unbelievable considering the size of this tool. For example easily planning a sprint, doing capacity tracking or even moving or changing issues can be very difficult and you may need to resort to plugins in their marketplace (with their own pricing).
Some of the more advanced functionality (like workflows) is a bit complex and confusing and requires quite a bit of studying.
Their pricing after the first tier (for startups) is just unbelievably expensive. It's a jump from $10 to $1000 when you add your 11th team member. Because of this we will sadly not keep using the software after that threshold.

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.

I use Jira for Project Management in my occupation. As a worker in a large enterprise, Jira does a phenomenal job of creating a fantastic user experience for both desktop and mobile. I think mobile project management is especially intuitive with this service. Where Jira stands apart from other standard project management tools is in its ability to track issues throughout an entire development lifecycle. Tickets are an essential component to keeping work organized and teams moving forward. The ability to collaborate via comments is unparalleled. Jira also offers extensive add-ons and pre-created templates for those just learning the service. When tracking projects, I never felt overly-encumbered by high learning curves or a clunky interface. Jira allowed me to work with many of the tools I am comfortable with and expand my potential.

From my experience, the largest pain-point / decision point between my team is on the issue of creating 'tickets'. While Jira is a very detail oriented application, this detail can sometimes become quite cumbersome. For example, the process of creating and resolving tickets can sometimes feel even longer than completing the task itself. Furthermore, it is difficult, if not impossible to close a ticket if you are not the creator. Therefore, project managers need to carry significant oversight as task statuses change. Therefore, tickets are very controversial but also an essential component to completing work successfully on this platform.

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.