Jira Reviews

We are using the product for general task management, largely. From a software development community perspective, obviously, we use the task management piece - the foundation to what leads into the development and the CI/CD pipelines and et cetera. Outside of that, it varies widely. At its very core, it's task management, however, then it's used by various functional areas within the company. For example, we have contracting and procurement that utilize it. And we have marketing that uses it and security, IT security, audit, compliance. Various functional areas across the company use Jira. We use it a lot. More and more business teams are using it today than were previously.

We also use it for reporting. With task management comes the Jira out-of-the-box reporting. We had Advanced Roadmaps before it was included in the product. And now that it's just rolled into the Data Center product, you obviously don't have to pay for it specifically anymore, however, that's the most scaled reporting that we have. Then, as far as any other apps are concerned, we really just use time and status for measuring continuous flow and have more of a Kanban approach. Of course, some workflow, add-ons, and things of that nature to add some value such as training for Jira.

I'm less concerned about marketplace apps due to the fact that, whether you go to Azure DevOps or Microsoft, or whether you go to Atlassian, there are countless apps out there that will extend the application itself. 

It's an organized, collaborative, transparent way of working and that's really helped the organization overall. Otherwise, many teams would still be managing work in Excel spreadsheets and/or SharePoint, which is just ridiculous. At least this provides some sort of structured approach that can easily be queried and have data extracted. I use Jira for everything at work. I don't even use email that much. It's through @mentions and all these different things. 

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.

We have different software projects. I primarily use Jira to define and plan projects for agile-based project management. We use different aspects. We have scrum-based management for some projects and different systems for others.

The agile framework works well, and I pretty much live by that. Everything, such as sprint management, is laid out.

It is easy to use and implement. It provides me with pretty much everything that I need to be able to do day-to-day planning, task management, and work log efficacy.

It is a great centralized tool for everything. You can use it for your local team management to communicate with your developers. You can also use it for your management team and for communicating with subcontractors to keep track of work products, work logs, and perform at the minute status.

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.

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.

My company doesn't use Jira for service desk management. My organization uses Jira in areas like user stories, ticket tracking for work, dashboards, and kanban boards.

The product has improved my organization since it provides a common point of reference for tracking work from different groups, including developers, QAs, and project management areas.