Jira Reviews

Workflow configuration (escalation, workflow chaining, conditions, validators, post-scripting, etc)

• Enforce role- and group-based permissions re: who can drag tickets, and when, on the agile boards.
• Instill true SLA-based reporting and escalation to keep work moving seamlessly through the process flow.

• Workflow management
• User permissions
• Native reporting capabilities in workflow
• Ticket status, etc

6 years

No

No

No

The forums and online documentation have been fine. I haven't needed to escalate beyond that.

The forums and online documentation have been fine. I haven't needed to escalate beyond that.

At my previous company they used Assembla. I switched them to JIRA which is more open in its project sharing as well as far more configurable.

JIRA has been very simple to use, no issues.

I've always done the implementations myself.

As an enabler of process and procedures, JIRA's ROI can be measured in that regard. Because we treat it like a tool and not an end unto itself, I've never measured it separately just for JIRA.

Including all plugins in my last job, ~$15,000 and $7,000 annually thereafter. That was very plugin-centric, however, due to the complexities and user interface solutions I implemented. Other deployments have been less expensive.

Bugzilla and other bug tracking tools were on the docket. We ultimately chose JIRA because of its UI polish and wide range of configuration options. When JIRA added Greenhopper, now JIRA Agile, that made the choice very simple going forward.

Read the online documentation, know what processes and procedures you wish to implement first, and keep it simple. Workflows can collapse under their own weight if they're overly complex for the sake of complexity, simply because "that's just the way things have always been done". Simplify simply simplify.

We use Jira to manage what is happening in our projects, such as application development lifecycles.

The most valuable features of Jira are the dashboards and user interface. The processes within Jira to monitor, maintain and release are beneficial. It is a continuous development solution.

I have used Jira within the past 12 months.

Jira is a reliable solution.

I have found Jira to be scalable.

The price of Jira could be lower.

I rate Jira an eight out of ten.

We use Jira for software development and issue tracking, enhancement requests, and software lifecycle management.

Jira has benefited the organization because it's necessary for doing our job well. We would need to have Jira or a similar tool. For example, it's could be similar to working with documents, you need Word or a similar tool.

The most valuable features of Jira are all the integrations with other systems. It's not the best in any specific area but it has lots of plug-ins and integrations.

Jira could improve the workflow, screen, and field configurability. They are lagging behind other solutions, such as Allegra in work system configurability.

It depends on your usage pattern because if it's more configurable, you can configure it to be a very different kind of tool which is a benefit.

I have been using Jira for approximately 10 years.

The performance is not very good for Jira but the reliability is good.

Jira can handle a lot of tasks. In my project, we have approximately 50,000 issues to be resolved and it worked well. However, the overall solution is slow.

We have approximately 25 employees using Jira in my organization of a total of 2,000 employees.

I use Jira moderately while other of my colleagues use it daily.

I have not used the support from Jira.

I have been using Allegra previously.

I was not around for the initial setup. However, I tried to configure it later and it is not easy. It is not as easy as it should be.

The solution is on the cloud, there is minimal maintenance.

The price of Jira is reasonable.

My advice to others thinking about implementing Jira is if you only want it for the standard flows and use it as an issue tracker in a software development setting, it is a good solution. We are using the online version. If you are in need of changing workflows or appearance, fields, screens, et cetera, Jira is not able to do this well or it's not possible at all.

Jira has found its place in our organization and it does those tasks. They should focus on speed and stability, and in that order. It's excellent with regards to preexisting integrations but it is poor at configurability.

Whether Jira is a good solution for you depends on your use case. From what I have seen creating different workflows in Jira is not good.

I rate Jira a five out of five.

Some of the use cases are for tracking issues and bugs.

I am responsible for an administering job for Atlassian Jira at my company. I'm working for some of the major IT companies in Kazakhstan.

The solution is deployed on-premises.

The solution is valuable because it's pretty flexible. It allows you to do a lot of stuff, and the functionality is pretty rich. It integrates well with other products, like GitLab, that we are currently intensely using at the company.

The solution could be more user-friendly.

I have been working with Jira within the past year.

The solution is pretty stable.

The solution is scalable. There are a few dozen users using this solution. We might increase the usage in the future.

I previously worked with ClickUp and would suggest using it. It's a competitor to Atlassian Jira.

When it comes to functionality and usability, I think ClickUp is better, but compared to Jira, ClickUp's drawback is their integrations with other products. The product is not old enough to be mature.

Jira is more flexible and more integrative with other products, and ClickUp is more user-friendly. The functionality is pretty rich.

I would rate this solution 9 out of 10. 

The only thing that I'd like to advise is to just monitor the market and keep an eye on comparison between the Jira and ClickUp.

The way it interfaces with Bitbucket and other things like that is valuable. Reporting and being able to link various issues or stories together are also valuable. We call them stories, and they're general reports.

I never had an issue with it at all. Everything I needed to do was always there. Everything is cool.

It should have Behavior Driven Development (BDD). There should be an option to add macros to help with that. A lot of people are using it now, and it would be nice if there was a way in there to be able to generate the BDD of commands whenever you're creating a story.

I have been using this solution for probably 8 to 10 years. I have used it at different companies. Cloud is the way they had it set up.

There were probably about 600 users, and they were from top management and all the way down to the testers. So, pretty much everybody used it.

I would rate it at least a 9 out of 10. That's because I never had any issues with it. It always did what I needed it to do.

We use Jira for project management for the development teams. Additionally, we do backtracking and managing the backlog but it is more of a development team tool.

There are a lot of plugins in Jira and we purchase the ones we need.

Jira can improve by making user management better. It is not easy to have visibility of who has the right to do what. Only the administrator has this visibility but there should be the option for other users too.

I have used Jira for approximately 10 years.

We have never had an issue with the stability of the solution.

We have approximately 400 people using the solution in my organization.

The support from Jira is good.

The configuration can be complicated, there are a lot of options.

We have a technical team that does the implementation and maintenance of the solutuon.

The basic price of Jira is reasonable, but for each plugin, we have to keep paying more. When you add it all up, it can be expensive. The main problem we face is we are forced to purchases plugin licenses for users who are not going to use them. For example, we have Jira licenses for approximately 450 people but if we only want a purchase a plugin for few people it is mandatory to buy the license for the 450 people who have Jira licensees. This is a problem because sometimes we need plugins for the product manager or for people in charge of the report, not everyone. For us, it can be very expensive in the end, they should alter this policy to allow plugins for only a set number of licenses.

My advice to those wanting to implement Jira is to have a lot of support. In our company, we started out small with only approximately 25 people and then we expanded quickly. Jira can be complex to manage, and it is better to have some advice or some people to help with the implementation.

I rate Jira an eight out of ten.

Our company follows the Agile methodology for software development, and this product is one of the best tools for companies that do so.

We regularly check the tasks assigned to us, day by day, and create a work log in that task according to what has been done.

You can check today's task assigned to you by using a custom filter, which you can create on your own. We can also make a customized dashboard user-wise.

Upper-level management can analyze the chart and get an overview of the project, giving them the ability to estimate the budget and release date of the project.

After purchasing Jira, we started shifting to it from the older software we used, like Bugzilla. Bugzilla was being used as our bug reporting tool but after the introduction of Jira, we began to use several of its features. We now use Jira for Scrum Planning, Bug Reporting, Time Tracking, and Budget Tracking.

Day by day, the transparency of the project improves and estimating the project release date becomes easier to do. It is also easy for management-level users to check the project's budget and estimate the release date for a specific feature.

Because there are a number of charts available, looking at them will assist you with any decision that is related to your project.

As a user of the Jira, rather than an administrator, the custom dashboard and custom filter are some of the best features from my perspective.

I can manage my own dashboard and by logging into my account every day, I can get information about the day's tasks assigned to me. I can also see my timeline chart, and using that, I can see and understand what has been done in the last week/month.

I have added a gadget on my dashboard that gives me regular updates on the bugs reported by the QA team.

Jira is one of the best software applications for project management and budget tracking, but it does have some issues, as follows:

• Firstly, the filtering feature can be improved to some degree.
• Because JIRA has so many features, it may take some time to obtain a general knowledge of each one.
• In order to enhance adoption in small and medium businesses, the cost should be improved.
• I believe it will be difficult for new users to understand.
• There are a limited number of gadgets accessible in Jira; thus, additional ones should be supported.

In our organization, we have been Jira since 2017.

Previously, we were using the Bugzilla bug tracking software for reporting bugs from the QA and FITs. Due to the number of problems that we had with it, we purchased Jira and have been using it for approximately five years.

The initial setup was easy, and we haven't found any difficulty in that.

The pricing is much higher than other similar solutions available in the market, and as such, the vendor should think about a price reduction to make this product more affordable.

We did not evaluate other options before implementing Jira.

Our primary use case is for project management, guiding the teams in our company. The solution allows you to create Scrum boards to deliver all the acquired stories within the Scrum Sprints. It also adapts to any other Jive methodology, like Kanban, and helps the creation of roadmaps for the software, production and implementation. We use it for day-to-day tasks, managing our stories, assigning tasks to different developers, and even integrating it with other system control tools to link the story's details. We are customers of Jira. 

The Jira user interface is really helpful because you can see the big picture regardless of what stage the task is at. You can define priorities and estimate times. If, for example, you're planning to move to Scrum, you need a project management tool; JIRA is perfect for that. It can also be used on personal projects because they offer a free plan with unlimited features to manage your project, define your backlog, and check the status of a project. 

The solution comes with multiple reporting charts so you can see the sprint burndown chart and other information. We previously had our own internal tools for Scrum, and moving to Jira was a total upgrade. There's no need to create new accounts for your users. You integrate company emails with an internal server, grant the user access and with their  company credentials, they can log into the platform. That's a pretty good feature. 

They could probably improve the integration with some of the automation tools and provide a specialized user interface suitable to their requirements. 

This is a very stable and reliable solution. The whole company uses it and we have around 500 employees. Our team adopted Jira recently but others in the company have been using it for a while. 

Jira is very scalable and allows for the integration with source control tools.

I haven't had to contact technical support. 

The initial setup was straightforward, we got access to it and started using it. They also provide you with documentation which helps if you are new to Scrum and new to the platform and features. 

There is an annual subscription fee based on the number of users. You can get a subscription for just 10 users, for small teams, and if you want more you can buy more. They have a standard and premium license. 

I would definitely recommend this product because it's scalable and easy to use. They provide best practice articles and quick start tutorials which are very helpful. If a new user has all the documentation, they can go from zero to hero very quickly.

I rate this solution a 10 out of 10.