Jira Reviews

I use Jira for maintaining our user stories, creating defects, and tracking progress. It's a part of my daily workflow. We have a dashboard where we manage stories within sprints, see backlog items, and keep track of both open and closed defects.

Jira facilitates bug tracking in our projects. When we find a defect, we log it in Jira and assign it to a developer. Once the developer fixes it, the defect moves into verification or the QA stage. The QA team validates the fix, and if everything is good, they close the defect. If needed, they can re-assign it back to me with comments.

I like how easy it is to collaborate. We can add comments and tag specific people, which is useful for both onshore and offshore teams. Here, we can tag the person easily, and Jira updates. The commenting feature keeps everyone updated on what work has been done. Jira has a lot of versatility, which makes it a handy tool.

Within Jira, we can tag stories by the current sprint and associate them with the developer working on them. We also use Jira to track story points and progress based on status. Once a story is ready for QA, the QA team can create sub-tasks directly in Jira and start their work. 

So, Jira is great for story management, but I'd like to see better tracking of employees' daily status for improved visibility for higher-level stakeholders.

The communication features could be enhanced. While Jira sends email notifications when comments are added, it would be great to have a more real-time chat function directly within the Jira dashboard. This would streamline communication when we need to clarify defects.

Also, test case management could be more user-friendly. When we add or update test cases, there should be a better way to organize them within the dashboard.

I've been using Jira for over seven, maybe eight years now.

I haven't experienced any stability problems myself, but there's always room for improvement. So, I would rate the stability an eight out of ten. I have not faced any major issues with Jira's stability.

I would rate the scalability an eight out of ten.

Everyone uses Jira. If something isn't working, that person likely isn't working either.

I've always worked with Jira since the beginning. It is a tool 

The initial setup of Jira is relatively straightforward.

Overall, I would rate the solution a seven out of ten.

I would recommend using it. It's the only tool where everyone can work within a single system, and we can track each other's records. That's a tool that helps people stay aligned.

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 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.

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! 

I use Jira in many cases when developing software. For example, I often use it for gathering software requirements, checking management, and issue tracking. Sometimes, I use it for planning my software development. I create some pictures and activities for my software planning, so I usually use Jira for my entire software development life cycle.

Jira is very useful for us, so we can set the resource and time because Jira gives us some dashboard. We can track and manage the due date of issues using Jira. It allows us to check the project status by using the Jira Dashboard.

There are many features in Jira. Our team uses Kanban and Sprint from Jira. It is very convenient to connect Jira with Teams and Slack. Jira's integration with our workflow is deep, and we rely on it heavily for software development. Jira's ability to streamline processes is crucial. It's a user-friendly tool that supports many kinds of APIs, and we can easily create dashboards.

Nowadays, AI is a very dominant function. I would like Jira to adapt AI functionality, which would be useful for finding issues or the status of the development plan. If AI functionality were integrated, it would provide useful features like searching for types of issues within Jira.

I have been working with Jira for eleven years.

Sometimes, there is a problem when Jira needs to sync data. During these times, we have to wait and can't use Jira. Although this kind of work is usually done over the weekend, it can cause trouble if we need to work during that time. After syncing, some errors occur but very rarely.

As a user, I find Jira to be a very scalable tool. We have no problems when using Jira, indicating it is quite scalable.

I usually ask for help from my colleagues. I do not contact Atlassian or their support directly.

Positive

I used Polarium before Jira, but I did not like it. I find Jira to be more user-friendly, with many types of APIs.

Our team makes tools using Jira API. It supports many APIs, so we can create our functions and tools. Overall, I'd rate the initial setup experience as an eight or nine from one to ten.

I have evaluated Polarium before.

I recommend Jira for project management. It is very convenient to manage issues or product plans and supports many kinds of APIs. It's easy to create dashboards. Overall, I would rate Jira nine out of ten.

My primary use case involves creating tickets and tracking them in Jira. I am responsible for planning iterations and PIs, and I make use of the AI features for summarizing tickets.

Jira is user-friendly and offers many features. The AI integration, particularly for summarizing tickets, is extremely valuable as it simplifies understanding ticket content without delving into detailed descriptions. The user interface is nice to use, and the workflow automation could potentially make operations simpler.

To improve Jira, providing proper documentation, examples, or snippets for scripting workflows would be beneficial. It would simplify the user experience, making the automation process easier.

I have been an end user of Jira for almost four years.

I do not see any issues with the stability of Jira.

I am not aware of the scalability specifics since I am just an end user.

Previously, we used Jama. It has been out of scope for a few years and Jira took its place. This was a company decision, and globally, our company is now using Microsoft Azure.

I am satisfied with Jira and would rate the overall solution a ten out of ten.