Jira Reviews

- Jira is used for bug tracking, issue tracking, and project management. - Jira has a powerful API, which means you can easily import or mash up your data with another system if need be – you haven’t locked yourself in! - Jira has been designed with a focus on task achievement, is instantly usable, and is flexible to work with. -you can create individual issue level security schemes, and specify the visibility of comments and work logs.

-At first, the documentation is typically light on needed information, is buggy, or is a little old. In general I found that I needed to do a bit of searching between the Jira documentation, issue tracking system, and the forums in order to get the information I needed, and it still didn't answer all of my questions. For the rest, I took a look at existing plug-ins to see how they had solved the problems. -I have found that Jira's customization can be very confusing in terms of configs and work flows, issue types, custom fields, etc. One should be confident and willing to do a lot of homework when taking on the implementation of anything other than the out-of-the-box functionality.

Jira is a bug and issue tracker primarily intended for software development. We use Jira internally to track all engagements within our team; as well as track bugs and issues for the web apps we develop. Jira is a very customizable product. It has a built in field builder that essentially lets you choose what fields you want to capture for your project. You can configure Jira’s custom fields at a system-wide, project specific and/or issue type level. Jira’s reporting component (or ‘filters’) make it easy to extract the information you want out of the system in several formats. Finally, Jira’s workflow features make it easy to define screens, based on business processes you might have.

I am currently using Jira for project management purposes, such as tracking the team and opening tickets. I am an admin in my project. When we start a new project, I open a new story in Jira for that project, and I open sub-tasks for that project. From there, I create backlogs. Our team is responsible for those backlogs. I have previously also used Jira for designing workflows for our enterprise.

It is helpful for tracking efforts for our projects. We have around 20 mandate projects, and Jira helps us to see how much effort goes into which feature and which team members have put effort into a project. It helps in anticipating the efforts for the next projects.

The ability to design your own workflows is a great feature.

The reporting part is a little bit difficult for me. It is not so easy. There should be a simpler way to track the efforts of our team. For example, in an Excel sheet, there is a feature for filtering. It would be much better if we can use something like that. Currently, for a complex query, we need to use Jira Query Language. Using Jira Query Language every time is not efficient for me.

Understanding the workflows can be a little bit difficult. For example, if you don't know the workflow well and you get an error, which is not a technical error, you won't be able to find the reason for that error.

I have been using Jira for the last 15 months.

There is no problem with its stability.

Its scalability is good. Too many people use Jira, and there is no problem with its scalability. It is a scalable product.

Our Jira team has five people, and our company has about 1,500 people who use Jira for tracking efforts. We are using it almost every week, and we don't plan to increase or decrease its usage.

We take support from the Jira team in our company. I didn't take support from Atlassian.

I have been with this company for about three years, and they were using Jira when I came here.

I didn't deploy Jira. We have a dedicated Jira team in our enterprise. There are five people on that team. This team supports two Jiras. They also support SoftTech Jira. It is used by about 20,000 people.

I don't remember the deployment time. The upgrade took 8 to 10 hours. We do maintenance frequently because when business processes change, many changes are required in the backend. Jira team takes care of the maintenance.

I would rate Jira an eight out of 10.

On-premises

It is easy to assign books, story styles, move across platforms and to different stakeholders while using this platform.

It has an easy UI that can easily plug-in to every level.

The CACD solutions on JIRA has some plugins, but they are not easily understandable or workable. 

More than five years.

It is definitely a stable product.

The scalability is fine.  

Tech support is good. 

We had a JIRA administrator help us with the setup, as well as an administration team. It took a bit of time to integrate the JIRA to our system.

In comparison to other solutions on the market, it is cost-effective. 

We looked at Micro Focus ALM vs JIRA, but it was quite expensive in comparison.

It is a user-friendly solution that is simple to use. 

JIRA is an issue tracking application, it in global development projects. JIRA helps teams to track and accomplish the items that need to be The great feature about JIRA is you can store the activity happening around an asset in one placeJIRA is useful in project management. It can reduce the rework in enterprise projects. You can also use JIRA Core for Project management, Task management, Process management, HR, Marketing, Legal and Finance projects. JIRA Core can be as per business projects need.

JIRA is very efficient. It helps us to create benchmark times to solve each ticket's severity. Burn down charts show your effort against the estimated time.

Active sprints. It is like a Kanban Board drag and drop backlog to assign, to do, and finish the task.

When creating Epic, Story, and Task, there is no provision to set estimated time. The estimated time can only be set once the ticket is created.

More than five years.

No.

No.

Excellent.

We have In-house project management tool. The report generation, burn chart are not so good. We Started to use Jira to  between different projects across geographic location

Straightforward.

In House

Its very nominal  prices per the features available.

No

JIRA is very good. With another tool, like Confluence, HipChat, Trello, Bitbucket, Bamboo, and FishEye. It creates a robust project and product management process.

I am the software developer manager and I use Jira to manage team performance. We're also starting to use Jira for our drives. I used Jira before, for creating user stories from boards, to discuss issues, and many other tasks. Today we use Jira, Confluence, and BitBucket in our work. We practice scrum in our organization.

It improved with many exiting features to manage user stories, planning and retrospective meetings very productive.

The documentation is very good.

The solution is stable.

You can scale the solution easily.

It's comparable to Azure DevOps.

It's a very complete product overall.

It would be ideal if Jira had future functionalities to integrate more easily with various aspects of code reviews.

It would be nice if, in the future, Jira worked a bit more like Azure DevOps in order to be able to manage work in progress and have the task measurements in strategies for the stories.

In the future, I would like to have traceability features. For example, when you create a task or a sub-task that's related to code. In this task, if we could create a method for retrieve customer information, that would be helpful. In that case, I would want to train with the source code later.

I'm new to the company. Although I've worked with Jira before, I've only been at this company for one week.

Atlassian solutions for me are very good solutions. They are very interesting and very productive. As a user, it is necessary to have a unique portal to make traceability between sub-tasks related to code or programming. You can create and screen or implement a function or a class, related for example to the code that you are pushing in the repository or commit in the repository. If I open the sub-task, I will see the code related to the sub-task. It's very similar like Azure DevOps. Azure DevOps, however, has this functionality for traceability. This functionality will be amazing that Jira would implement something similar.

I prefer to use Azure DevOps instead of Jira for stability or the frequency of use. In my case, for example, I feel that more users, more companies don't think Azure DevOps makes a good choice due to the fact that the cost is higher than Jira.

The scalability is very good if you're carrying a lot of projects here, and if the company needs to have a lot of people to PEA development centers in Mexico. Our technicians can easily test the tool and scale it in order to develop projects.

We do plan to increase usage. We're already training more users. We're increasing quickly so that our teams will be ready for upcoming projects.

We have manuals, technical support, and also technical specialists in the company. I haven't had the opportunity to use directly call the technical support from Atlassian, however, the technical documentation that I have reviewed is excellent. We're satisfied with the level of service we have access to.

We also use Azure DevOps. They are both very similar. The main difference is Azure offers traceability.

The solution is easy to implement. We have the cloud version of Jira in the company, and we don't worry about maintenance, it's automatic.

The cost of Jira is okay. It's better than Azure DevOps. We don't have any licensing fees that I know of.

While I'm new to the company, it's my understanding that it is a partner of Atlassian.

We use the latest version of the solution, as we use the cloud, which updates automatically.

Our company has both Azure DevOps and Jira. I use Jira, and Azure DevOps is used for other purposes. Most projects, all projects that are using Azure DevOps are legacy projects. The new projects and new solutions are using Jira.

On a scale from one to ten, I'd rate Jira at a ten. It's a very good product.

Both tools, Azure DevOps and Jira are at the same level. In terms of preference, I typically choose Azure DevOps for familiarity but not for features. For features, both are the same. For example, Jira has amazing features that Azure DevOps doesn't have, and also Azure DevOps has the flexibility that I like very much. Both tools have different interesting aspects. However, if Atlassian would implement traceability, I would prefer to use Atlassian. For me, it's more complete and allows for smaller teams than Azure DevOps.

Public Cloud

We use one version of Jira internally and we also have another version of Jira that we use externally for our customer. We've been using it for both.

Internally we use Jira for our own implementations and capturing requirements and our customers are using the whole tool for the whole software development life cycle. They're using it for the full life cycle of the product.

The Defect section could be improved. When you're trying to keep track of the requirements and the Defect section, this setup could be done better.

I was struggling to set it up. I wish the whole workflow process was easier to set up. You put the requirements in and then you send it to the developer. They get a notification. Then they go into Jira.

We have been using Jira over the last 12 months or more.

On a scale of one to ten, I would give Jira a seven.

To be a ten, there should be more options where you just click and drag. That would be nice. It's hard to copy and paste requirements. You lose your formatting and everything. So just simple navigation stuff should be improved.

We primarily use the solution for bug tracking. It's for customer support purposes.

The solution is quite easy to use. It's very user-friendly. The product is very easy to understand.

The solution offers very good tools for Agile teams.

The pricing of the product is very good. It's not too expensive.

We're more focused on other solutions. Jira could be more, for example, like Micro Focus, which is what I mostly work with currently.

I've been using the solution for about seven months at this point.

I'm not sure if the product is stable or not. I don't have any insights into that aspect of the product.

I don't know if the solution is scalable or not. It's not an aspect of the solution I'm responsible for.

I'm not sure how many users are on the solution currently. I'm not sure if there is a plan to increase usage just yet. That might be a question for our company in the next year or so.

We tend to handle technical support internally for the most part. I can't really speak to the actual technical support from Jira as I haven't dealt with them for the most part.

We are also using Micro Focus.

I'm more on the customer support side of the product. I didn't really handle the setup process. Other members of my team handled the implementation.

We've found the pricing to be quite good. It's not overly expensive. It's very reasonable and affordable for companies to implement.

We're just customers and end-users. We don't have a specific business relationship with Jira.

I'm not sure of which version of the solution we're using currently. It's my understanding that it is the latest version. I'm not sure if we are using the cloud or the on-premises deployment version.

Currently, I'm more focused on the Micro Focus product as opposed to Jira. That's more where my expertise is at the moment.

That said, it's pretty easy to use and I would recommend Jira to other organizations for that reason.

Overall, I would rate it at a seven out of ten.

We use JIRA for maintaining tasks and bugs. Overall, we love using JIRA because it performs very well with a lot of tasks and a lot of dashboards.

Having a tool to manage all your tasks and all your bugs is very useful for any company. We use it a lot to keep track, to see how our development is going and how automation is going.

We use a lot of dashboards and a lot of queries to search for specific bugs related to specific versions. Also, we can provide it to all of our users throughout the company.

The ability to change and rewrite tasks is valuable. You can add a lot of columns, change the owners and the change the components. It gives you a lot of flexibility between the teams.

I would like to see it connecting to Git. That could be useful. We use it for Stash, but I think there is one for Git also. I don't know if it's a plug-in that exists already, but that could be nice.

We have had no problems with stability. We're doing maintenance upgrades, but it has working well all the time.

We're not dealing with the scalability because we're not IT, but I don't think there is a problem with scalability.

We used Bugzilla but its UI was not as user-friendly. The end-user experience was very basic because it's a free tool. It's important to us that QA be able to track the issues and, of course, for the developers to be able to track all the tasks. So we're looking for the balance between performance of the user interface and the UI for the other workers in the company.

I would rate it at nine out of 10 because there is always room for improvement, but we love this tool and we use it a lot.

I would recommend JIRA. Compare all the tools for bug and task management. After that, you'll see that JIRA is by far the best.