Jira Reviews

We use Jira for various purposes. Firstly, we use it to gather requirements by raising tickets and tracking them in the system. Additionally, we utilize it for bug-tracking. 

What I really like about Jira is that it ticks off all the boxes for any agile project. It's easy to set up, easy to use, and it has excellent notification features. Jira is the top choice for anyone working on agile projects like ours.

The tool lacks support for testing aspects, which means we often rely on integrations with other tools for testing purposes. If Jira could incorporate testing modules within its platform, it would eliminate the need for external integrations.

I have been working with the product for five years. 

I rate the tool's stability an eight out of ten. 

Jira is scalable. I rate it an eight out of ten; we have nearly 100 users. 

Installing Jira isn't difficult, but our administrator or IT help usually handles it, so I'm not directly involved in the installation process. We have around 50 resources for deployment and maintenance. 

Jira is worth the money. 

I rate the tool's pricing a five out of ten. It's paid yearly. 

My advice would be to explore the different licensing options available for Jira. There's a level of customization in pricing to tailor it to your needs. I rate it a ten out of ten. 

I have managed various projects using Jira, including tasks for the government, the environmental sector, education, and donation applications. I have also worked on multiple websites for marketing and search engine optimization.

The most valuable feature of Jira for sprint planning is the timeline feature, which allows for better visualization and planning of releases. However, there are limitations compared to other tools like TFS, which offer more flexibility with features like user stories, epics, and initiatives without extra fees. Despite this, Jira's ease of adding user stories to sprints and connecting them to releases is very good.

Jira lacks easy capacity calculation compared to TFS, making it harder to know how much work to allocate to each specialist. In TFS, it is simpler to manage capacity and reassign tasks when necessary. Additionally, a feature in TFS automatically creates relevant tasks based on a code snippet linked to a user story, saving time and effort in task creation. This feature isn't available in Jira, which makes task management less streamlined.

I have been working with Jira for almost two years.

Jira is expensive.

I recommend Jira for its usability, especially for writing user stories and adjusting metrics, though it is expensive.

Jira has improved our team's productivity mainly through integrations, particularly with Slack. This integration helps keep track of changes made to user stories, providing alerts for any updates. 

I would recommend Jira for managing projects in agile environments, but certain features are necessary for better functionality, like improved capacity calculation and streamlined task creation. Additionally, Jira can be expensive, so essential tools like test planning should ideally be included in the standard subscription rather than requiring costly third-party plugins.

Overall, I would rate Jira as a seven out of ten.

We are using the solution for project management.

The solution helps to track issues related to project management. It helps with different activities like assigning tasks and reacting to issues.

Linking the issues to members in the team and outside the team has been valuable. Jira's reporting and analytics features are very important for analyzing the entire sprint activity at the end or middle of the sprint. The tool helps track the capacity, velocity, assignments, and different team members’ activities. We can track the entire sprint speed. The burndown charts help track projects. Over time, the tool has completely adapted to our project's scanning needs. We use it however we want and change the settings as we want. So it's quite adaptive.

The product must provide more automation. Scripts should be more readily available for implementing projects. It should provide quick launch features to build projects.

I have been using the solution for three years.

I rate the tool’s stability an eight to nine out of ten. It's quite stable. We haven't faced any issues.

The tool is quite scalable. It was quite useful for our projects. I rate the scalability eight out of ten. We have 30 to 40 users. We use the product daily.

I have used Azure for some projects. We switched to Jira because it is easy to implement and use. It is good for smaller projects. It is easier to start using Jira than other products.

The initial setup was quite easy. I rate the ease of setup an eight out of ten. The product is deployed on the cloud.

The price is quite competitive. I rate the pricing a seven to eight out of ten.

I will recommend the product to others. It is easy to use and implement. Overall, I rate the solution a nine out of ten.

We use the solution primarily for the IT development processes since we also develop some internal software and integrations. We use it for IT support. We also use the project management features. We help create some custom projects within Jira and assign or dedicate some of the projects to top-level projects. Some are epic projects. We have our own custom project structure within Jira.

The product provides high flexibility to create new workflows quickly. There isn't much work. We use it to track developers' and other IT personnel's time. Everybody enters all the tasks so we can create reports quickly. The integrations are fairly straightforward. The reporting and analytics feature considerably impacts our project management and decision-making process. I rate the impact an eight out of ten.

We had quite a lot of issues integrating BMC Remedy and Jira. They're different. A lot of information needs to be exchanged. The changes that need to be promoted from one on-site to another are challenging. It is easier to integrate Jira with other systems than BMC Remedy. The database has grown since we've been using the tool for 12 years. The performance and stability are visibly degrading since the database has been growing every year.

I have been using the solution for 12 years.

I rate the stability a six out of ten. We have a large database.

The demand is growing. Even though we put in additional and better hardware, the scalability is not what we would like it to be. I rate the scalability a four or five out of ten.

The deployment took a couple of months. We needed a team of five to ten people to deploy the product. I rate the ease of setup a nine out of ten.

I rate the pricing a seven out of ten. The tool is expensive.

We looked for an alternative since Jira’s licensing is expensive. We tested five to six other products. However, we chose Jira because it is quite a solid product. We had a lot of data to migrate and didn't want to spend too much time doing that.

We don't use bug tracking in Jira. I haven't contacted support at all. I’m not responsible for maintaining the Jira deployment. My colleagues take care of it. I might recommend the solution depending on the size and purpose someone wants to use it for. If we don't have personnel to administer Jira, we will have to hire a relatively expensive company to do it. Overall, I rate the product a seven out of ten.

Jira is used for field management and task assignment. We use Jira on the project management side. We also use storyboards for planning and scheduling. It can be used for tracking and managing issues. It provides a dashboard showing what's open and what's closed. We can access all these details there.

The easy tracking feature is available, but it serves as the foundation of Jira within the bundle. Apart from that, the software supports individual development and testing with LiveStack. Previously, we use Insight to identify additional defects, which could be related to multiple test cases. A single defect might encompass multiple test cases, and vice versa, with different defects linked to various test cases. Having a separate defect management system would allow for one-to-one, one-to-many, or many-to-one mappings. We are unable to perform all of these tasks with the current issue tracker.

The integration of other open source tools with Jira is very useful. It allows us to create documents and transcriptions, making it versatile beyond software development. Jira was originally developed for IT projects, but it can also be effectively utilized for non-IT sectors. It enables tracking and maintenance of projects outside the IT domain as well. I recommend the solution.

The reporting feature is very beneficial. Customers can report using the predefined report template.

The workflow is fine, but it's only integrated within Jira and not with other tools. Additionally, the SQL query is also very helpful.

In project communication, it is necessary to train every new member who joins us for Jira. Apart from training, using Jira for project planning and scheduling can be very helpful.

Remote collaboration is helpful. We need to conduct screen sharing sessions with everyone, it would be even better if Jira could provide integrated screen sharing capabilities and enhanced email communication features. Therefore, the release of a MailServer feature within Jira would be beneficial.

If I want to create a Jira account, I need an email ID. If Jira will provide the same functionality as Gmail, such as a mail server, then collaborating via Jira email will be possible. Additionally, for trained individuals, we can share screens within Jira itself.

I have been using Jira for over 5 years.

The product is stable.

I rate the solution’s stability a 9 out of 10.

We have three member along with a founder and co-founder using this solution.

I rate the scalability a 9 out of 10.

The initial setup is easy but if any new ecommerce is coming into picture, it can be difficult.

I rate the initial setup a 10 out of 10, where one is difficult, and ten is easy.

We are using for free version. The pricing is very cheap and has a very nominal fee.

Overall, I rate the solution a 10 out of 10.

Jira is used for all the project management, on all the stages of project management. So then we create a Kanban board and move on to creating the stories.

We create the story points, break down the requirements, and then create the Sprint accordingly. Based on that, we can manage in Jira how many user stories we will pick in what Sprint. And based on the dependencies of the user stories, this is the flexibility that Jira provides. Then we have also got various, you know, sub-tasks, which we have to complete to accomplish the DoD (Definition of Done). We can mark the Sprint as complete when these particular tasks are completed. So that gives very good monitoring of the project where the project is

going on.

When it comes to the testing part, so testing is end-to-end on Jira. We can take the user stories based on the acceptance criteria. The test cases are created in Jira, and the business analyst team reviews those test cases. Based on their feedback, the test cases are updated. Those test cases are being executed. So there is clear tracking of the test execution, and all the test cases are also linked with the user storage. We have end-to-end tracking of what test case is executed for what user story. So that is the best part of Jira.

The monitoring, flexibility and tracking are really good in Jira.

When we use the plugin in Jira so, there are two different systems which we are working on, Jira and the X-ray plugin. The X-ray plugin should be incorporated into Jira because we have to fetch two reports. One report is faxed through Jira, and one can be faxed through X-ray. So there needs to be clarity about which the Jira team should reflect.

I have been using Jira for eight years. 

Jira is a stable product. I have seen the growth in the solution’s stability for the last eight years. The current version is quite stable and is a robust system.

Overall, the solution is scalable. Jira is quite easy to scale. If we have five projects working on Jira and we have about five more projects to be incorporated, it's easy to install Jira for those five projects as well. Presently, twenty five thousand users are using Jira. 

We have been using this for the last eight years and we are quite accustomed to that. We don’t need much support from Jira or Atlassian. Yes, but we have got an enterprise version of that, and their support is quite quick.

Positive

I was using HPE Quality Management Tool.

The initial setup of Jira is very easy. I have been an administrator, so I would say that because used to it. But in comparison to other systems, yeah, it’s quite easy and user-friendly. The deployment takes two to three days of time. Forty people are required for the maintenance of the solution.

I implemented it myself as an administrator of Jira.

Compared to the value Jira provides, it’s not that expensive. It has an yearly licensing cost.

Use all the reports which are generated. You have to make a system for the process. Here is a small example during a subtask. The time input via the source is not mandatory. But you have to make it mandatory either from the back end.

You’ll not be able to fetch the reports on the performance, the health of the project, capacity management, or IT management if the data is not input properly. So this is something which people most people don’t take care of as a Jira planning. But when you plan a project, you have to plan these things.

I rate the overall solution a seven out of ten.

I use the solution for agile project management. We use it to break down the project into tasks. 

Jira improved our team collaboration by providing visual visibility and transparency. Everyone could see what tasks were being worked on and the progress made. The development team updated task statuses, making tracking progress and planning sprints easy. If there were any impediments or challenges, we addressed them. This process helped us track our progress.

What I find most valuable in Jira is overall architecture, especially the ability to create dashboards. This feature allows me to gain insights into my projects.

Jira's reporting and analytics features have been super helpful for me in managing my projects. I can easily generate reports and create dashboards to track progress. I can export data to Excel, making it easier to work with outside Jira. The filters in Jira also make it simple to get exactly the data I need.

The tool has been really helpful for our remote team, especially with all our scrum events like daily stand-ups. Having Jira right there during those meetings helps us discuss tasks and settings easily. Plus, it integrates with Microsoft Teams, which we've found handy. It gives us a clear picture of what everyone's working on, so if there's a lack of progress on something, we can quickly address it through Slack or a call.

The solution lacks integration with visualization tools like Power BI or Tableau, which would be beneficial for better insights.

I have been working with Jira for three years. 

I haven't experienced any performance issues with the product.

Currently, our project has a team of around 40-50 people, plus additional members from the client side who are using Jira. It is scalable. 

I haven't needed to escalate any questions to Jira's technical support. Whenever I've had doubts or needed help with something, I've usually found answers in the Jira community. 

Compared to Microsoft Azure DevOps, Jira is more user-friendly. It offers helpful video tutorials and other features that make it easier to use. One thing I appreciate about Jira is its ability to create and customise reports and dashboards.

Setting up Jira was straightforward. The online videos guided me through the process. The program is more about automated deployment, not manual deployment. I wasn't directly involved in the deployment process. Usually, it's handled by the Jira administrator. I mainly focused on my role as a project administrator within Jira.

Maintaining the tool is easy; there's no problem with it. You can even add things from your Excel sheets into Jira. For example, if you have user tasks in Excel, you can easily upload them.

Our client handles the licensing aspect. They have not yet purchased the premium version. 

We plan to integrate the tool with AWS. I rate it an eight out of ten. 

I use it for hours tracking with Tempo login, task management, project management, and time booking with the Tempo plugin.

Jira supports our bug-tracking process. We use reports to track bugs. We create reports, and then the issues are fixed.

We have also customized Jira with add-ons and integrations. For example, we use the Tempo plugin for time booking.

I like that there are a lot of features and options, like the Kanban board and other ways to customize projects, columns, and fields.

Jira's reporting and analytics features are also good. 

For project management analytics, we use features like cost tracking, etc.

Integration is good. A lot of tools we use can connect to Jira using the API, making things easier.

ClickUp is a good alternative to Jira, so they have a better interface [GUI]. I don't like Jira's graphical interface - it could be more user-friendly. Jira looks old school. 

Also, the administration part of Jira should be simpler for project managers and Jira administrators. It has many configuration areas, which can be confusing.

So, the administration part could be more simplified. 

I have been using it for ten years. 

It is quite stable. I would rate the stability a ten out of ten. 

ClickUp has more features, so I'd rate Jira around seven for scalability.

On average there are around 500 end users using this solution. 

For some projects I'm involved in, we use the cloud version. Most of our clients are moving to the cloud.

On-premise, because it has more features than the cloud version, or at least the cloud versions our clients have purchased.

Overall, I would rate the solution a nine out of ten. I would recommend using this solution. Go for it!