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.

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

Jira has a much better user interface that other similar products, along with a better price point. In fact, I've migrated teams from other applications to Jira. It allows user to configure screens, workflows, and field as desired. You can go from basic and plain to heavily customized schemes. It also integrates well with other SaaS products.

The out-of-box gadgets, dashboards, and reporting is very limited in terms of data reporting. To get better and deep metrics, you need to purchase marketplace plugins.

As someone who is not a developer but needs to know what they're working on, Jira is very strong. I can easily see what the development board looks like, as well as view work that individual development teams are working on.

Sometimes I believe Jira is a little hard to navigate as someone who is not in the product all day, every day, but that would be my only criticism. It's a big one, though. I want to quickly see what's going on, not have to dig and find it. That could just be how we have it setup, though!

JIRA certainly has a lot of features that should make Project Management easy. The mobile app is adequate, and the web site works well enough. There are a whole lot of places to enter data, which ends up being a bit of a downfall. When JIRA is set up well, it does support PM. When it is used as a vanilla Agile product, I think it falls behind other offerings.

JIRA has so many configuration points that it takes forever to get it working properly for your team. They have also been changing the UI a lot recently, which has obscured where some data is, which - predictably - has slowed down our use. If JIRA could get a more consistent UI, I feel it could be a much better product.

It is a feature packed program that helps teams collaborate using a ticketing system. Much easier way to work with team members to fix issues, deploy updates and collaborate. Using this system between employees, departments, consultants and others we have been able to streamline collaboration on projects. It also has a lot of integration, including with Slack, to expedite notifications.

There is definitely a learning curve with this project and it can be a little hard to get the hang of, but once you do, the UI of the program will make sense.

We use JIRA online and it's dead simple to create and manage complex tasks. I love the ability to integrate with great packages like Confluence (which is SOOOO much better than Slack!).

Getting new employees up to speed on using the software is more time consuming that it should be. I'd prefer a more intuitive UI.

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.

Agile development on Jira is great. The ecosystem allows me to track my time, organize my issues into tasks and sub-tasks, track when things get done, create estimates, and organize complex projects into smaller and simpler pieces.

The support is pretty ignorant of their user-base on several issues and refuse to add new features that would benefit hundreds, if not thousands. It can be very tricky to migrate, update, or set up. Plugins can cost money and it can add up, though I haven't spent too much at all for the value I received.

- Jira has the most critical features that every small to enterprise companies use to manage project management, application development, time tracking, workflow automation for various business use-cases, integrations with external applications like Copado (CI/CD) tool for Salesforce
- Jira has very important usage in our company. All the teams uses Jira to manage all the deliverables and for tracking project management, feature releases, etc.

- The pricing of jira can be cheaper when compared to other alternate solutions available in the market
- The support of Jira can be more available in all times to resolve critical issues
- The UI can be more customized to better fit every customer needs without lot of overhead time

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.

I love the quick and easy setup of JIRA spaces and it's integration with other Atlassian products. There are also a lot of third-party integrations to help fill-in the gaps.

JIRA is a beast. Plain and simple. Actually that's just it...it's not plain and simple. You have to have a good grasp of what you want from it to make sure you get what you really need. It is not friendly for the non-technical user looking to create a workspace.

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.

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.

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.