Jira Reviews

We use Jira primarily for project management within the organization. It helps us manage tasks, bug management, and tracking tickets effectively. We assign tickets to individual team members and track them easily.

For project management, Jira has helped facilitate efficient task segregation and allocation to employees. It allows us to track projects comprehensively and improves the overall management from a project perspective.

We manage our sprints and backlog using Jira.

It is implemented for everything. The project works whether it's in development or production. Everything has to go through Jira. Jira is integral to it all.

So, Jira has been instrumental in book tracking for our team.

For software development, we use the Kanban board or the Sprint board to manage backlogs, sprint management, and sprint reports. All communication happens through Jira. This includes requirement details, questions, estimates, and actual hours worked. We use Jira extensively.

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.

We follow an Agile framework and use Jira for sprint planning and management.

The scrum dashboard is the product's most important feature. It provides an overview of tasks, who is working on what, and the status of each task.

It offers very good APIs for creating custom integrations and has many built-in integrations with other tools.

I use Jira for sprint planning and tracking projects. I can create boards on it. And then I just have backlogs, and I just basically plan and sprint for the next two weeks, and you just put anything on the to-do list, doing, and done through the board. So it's very simple. It’s all drag and drop. There’s nothing too complex around it. 

The main thing is making sure whatever you're planning for your sprint is covered there, and then you can run reports after that.  Sometimes, the key issue I've seen with project failures is when the sprint planning isn't comprehensive enough.  It’s not being covered. But generally, it's very similar to Microsoft Project, in some ways because you can still create those Kanban boards and run things, but nothing too crazy.

Our client engagements are usually for a specific period. From an analytics perspective, long-term tracking is probably better handled on the client's end, not ours, as we're not there long enough to gather meaningful data.

I am aware of the bug-tracking function in Jira. We mention the bug on the ticket itself, whatever ticket we're working on, but we don't track the bug separately. Only because once the ticket closes, the bug sort of closes with it. For ongoing bugs, that's a different place to store the information, not on Jira. That's just my opinion. 

Anything that's open should be stored in Jira; otherwise, it will get lost. So, I don't feel that's the right place to keep ongoing bugs.

It is easy to integrate Jira within our current IT environment. Jira has connectors and supports various integrations, but again, we don't overcomplicate our setup. We keep our Jira usage simple. I've generally seen it integrate well, so I don't think it should be an issue.

We just use it for very basic purposes. 

I use Jira for project management. 

Jira is designed for issue tracking, making the process much easier than traditional methods like paper-based tracking. It is number one for agile management.

Jira's reporting and analytics features provide a clear picture of what happens, making them good. I use it in my work. 

In our organization, we use Jira for project management and usually use the Scrum project type. We might adjust the workflows and stages to better suit our needs, but we mostly use the default functionalities it offers to manage our projects.

It's flexible and customizable, and we frequently use it with customized workflows and dashboards to track defects. Jira works well with tools like TestRail and Clarity, which help with test management. It has various APIs.

Jira's reporting and analytics features support project management by providing useful out-of-the-box reports. These include burn-down charts for Agile project management and various other reports. These default reports typically cover around 60 percent of users' needs. Users can customize their reports and dashboards for the remaining needs, which usually fulfill about 80-85 percent of requirements. Add-ons can be used for the remaining small gap.

The tool mainly supports remote or distributed team collaboration through its cloud version, accessible from anywhere. Within Jira, you can communicate effectively with team members by assigning issues, leaving comments, and referencing people for notifications. While direct communication features within the tool are decent but not outstanding, integration with tools like Slack or Teams can enhance collaboration further.

Jira could be easier to use, especially for administrative tasks. It's quite complex, so it's important to understand it well. While the reporting and dashboards are good, there's room for improvement in some areas where extra features would be helpful.

Sometimes, we need add-ons in the product, especially for reporting. While you can get these through add-ons, they can be pricey. The licensing system for add-ons might also seem unfair because you often have to pay for all users, even if only a few use the add-on. So, maybe the licensing model could be adjusted.

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.