Jira Reviews

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.  

I'm working on creating test cases and one test. I also have an overview of the Sprint.

In general, the GUI is nice. 

The part when it comes to the testing area is a bit hard to handle. The screen is too small, you can't really read what you're typing in, and it's only for the testing area. It looks like they have pressed in more than the UI system could handle to display it properly.

I have been working with Jira for about eight months.

Jira seems like a stable product, but sometimes I'm losing data.

As a totally different team does the entire setup, I don't know if it's scalable. But we have about 150 users.

To be quite honest, at the end of the day, a tool is just a tool. For me personally, it's hard to say this tool is much better than the other. From just what I know so far, Micro Focus Octane looks a bit more modern. But I don't know which Jira version we're using at the moment. Octane looks a bit more integrated, it looks a bit newer, but would I buy a tool because of that? Certainly not.

I would recommend Jira for Sprint management. But when it comes to documentation of manual tests, I would say, "Okay, you can buy it if you want to have one package, but you can also have a look at something different."

On a scale from one to ten, I would give Jira a solid eight.

We are mainly using it for project management and issue tracking. It is used by development, QA, and IT operations. It really goes through the whole gamut of project management.

We are not using its latest version. We are usually a little bit behind on versions.

Jira is a pretty capable product, and a lot of features are valuable. We value being able to set up separate projects and configure teams in them, set up sprints, and manage our sprints with its history tracking. These are all very useful features. It has been a very popular product for our work.

Because I am a developer, I would like integration with Git Source Code Management so that for tickets, we can reference the code where the change has happened and where the issue is. This feature might be there, and I probably haven't discovered it.

I have been using this solution for probably six years.

Its stability has been very good. Every once in a while, we have a problem, and the service stops working. I don't think we have a very robust installation of it, but if there is an issue, it is back online very quickly.

Most of the issues are probably related to the server needing patching or something else. It may not be running on the appropriate size hardware. I know it is not a well-funded product at our office.

It is impressive. We have all our projects on it, and we haven't really had reports of any issues. We haven't yet stretched it to its limitations, but it has managed to meet our requirements, even in this minimal deployment. I am pretty impressed. 

I didn't directly contact them, but I am sure at some point we have. We usually have a contact person, and we pay for the full support.

We are adopting multiple products, such as ServiceNow, but they do different things and are for different purposes. There is a talk about replacing Jira with ServiceNow, and we're not too happy with it because we all liked Jira, but sometimes this kind of stuff happens. ServiceNow does have crossover features, but it gets into problems for us when changing from one system to another.

I didn't set it up, but I haven't heard of any issues with the implementation of it. It seems to be very straightforward.

I would recommend this product. Overall, it is a good product. It supports scrum and agile developments. It has a lot of benefits that can be applied very quickly in organizations.

I would advise others to do a test installation and make sure that it fits their needs. Experiment with the multitudes of features that it has. I know there are lots of modules. There are probably many features that we are not using. 

I would give it very high marks. I would rate Jira a nine out of ten. There is always something you could improve on it.

I use it for project management and agile scrum projects. I am a manager, and I work with backlog tools and sprint plans. I only use Jira for backlogs, sprint reviews, and data reports. Our project manager is the person who is really working with Jira along with the team. We also have Confluence and Bitbucket. We use CloudBees and DevOps for the deployment of the environment.

It is easy to deploy in the cloud and other environments. It is also easy to view the reports of the sprint review or the sprint plan and the relation between the backlog and the repositories.

I am not sure if Jira can be integrated with our ERP. We have our ERP for the cost estimates or measurements. It would be nice if we can check or view a plan with the real cost. Currently, we have to do a double check of costs. It would be better to be able to integrate it with Jira.

I have been using Jira for almost one year.

I don't work too much with Jira. I use it only to see the reports, and I don't feel that there are many bugs. It is stable.

It is not too expensive. It is just comparative to other tools like Microsoft Teams.

I would recommend this solution. We are interested in migrating to Jira and using it as our internal tool for agile projects and for controlling the IT software development cycle for projects like consulting or API. It will be more used for agile projects. It is a good tool. We also have the latest version of Microsoft Teams, but it is limited. It is better to use Jira.

I would rate Jira a nine out of ten.

We have a development team and we use Jira to manage our projects. We use several products by Atlassian whenever we create and work on a new project.

We have scrum masters who write new project stories, which are tracked by Jira.

The most valuable feature is project management.

The integration and management features need to be improved.

When you first start to use the interface, it is confusing.

We have been using Jira for about one year.

In my company, we have a lot of knowledge and experience with Atlassian products. We have not needed to contact technical support.

I have also used ALM Synchronizer and I find that it is better because it is easier to manage and it is a more agile tool.

My advice for anybody who is implementing Jira is to install the plugin from Micro Focus because it is a better way to manage the interrelationship between these two tools.

Overall, my experience with Jira is pretty good.

I would rate this solution a nine out of ten.

Some of the features that are most important to me of JIRA Agile are the sprint planning, being able to write user stories and being able to use task management. JIRA appears to be constantly evolving, developing, and adding new features throughout the process. 

I have had problems with performance and unresponsiveness. All of a sudden, the performance slowed down and I had a number of users that could not use the tool but, JIRA support responded immediately. Within a couple of hours, the problem was resolved.

I would give tech support a rating of eight out of ten.

I have prior experience with what was originally called HP Quality Center but is now called Micro Focus ALM. In comparing Micro Focus ALM vs Jira,I did not find it as intuitive or user-friendly as JIRA. I also have experience with and have compared CA Agile Central vs JIRA, but my preference is always JIRA because it is more established and very intuitive to work with.

The setup was on-premises and it was basically installing it on a server. I found the setup relatively easy and straightforward to install from scratch, in-house.

My advice to future users is to check out sources like YouTube and look at the main features you want. Potentially with JIRA, particularly with the cloud version, they have a seven day trial. I suggest that future users sign up for the free trial to make sure the features of JIRA meet their personal requirements. Also, the user should make sure that JIRA is a good fit for the user's organization.