Jira Reviews

I absolutely love Jira—it makes project management a breeze! The @mentions keep everyone informed, the API integrates smoothly with my other tools, and the access controls keep everything secure. The activity dashboard, tracking, and reporting features are fantastic for staying on top of progress, while the Agile methodologies and alerts ensure I can manage workflows and stay updated effortlessly.

I found that the interface can feel a bit overwhelming for new users, and it took me some time to get fully comfortable with all its features. However, once I got the hang of it, Jira became incredibly powerful and efficient!

Features such as Scrum boards, kanban board, sprints, and backlogs are great for teams who follow agile methodology. We can customize workflows, fields, and issue types as per our needs. Most important feature is that it enables us to track the project progress in realtime. In addition, it is compatible with many external apps and facilitate the smooth workflow.

Extensive features and customization options can make the initial setup complex, especially for newcomers to project management tools. Its lacks built-in idea management functionality, we need to use some additional tools for brainstorming and concept development. Also, the pricing seems to be bit high and it may not be an affordable option for small teams or startups with limited budgets.

Customizable workflows , where the tool can be customized based on the project type and needs like agile and scrum.
Powerful issue tracking, where you can track the project issues and you have dashboards to monitor and prioritize
Multiple plugin options

Though , it is an issue tracking tool , i doesn't have an inbuilt testing toll feature. We need to integrate this with third party tools for testing.
Availability of lot of plugins are creating chances to over doing the info and makes it complex

Jira is very flexible and can be used for different use cases, eg: project management, issue tracker, road maps etc.
It is quite easy to configure compared to other generic project management tools.

The transition from old user interface to new one, it is very confusing, the UI is not consistent when we visit URLs from email notifications.
Compared to other generic tools, Jira is quite easy but still it is not easy to setup, it takes quite a few days to configure the system as per needs. It would be great if there were boilerplate templates.

Jira is an excellent project management tool. It is the best option for bug tracking and agile project management. Multiple teams can use Jira at the same time leading to a lot of integrations. Teams including product strategy, product design, and product development can collaborate together leading to improvement in project. Each team can track their individual milestones, deliverables, and tasks using the filter and search functionality. If you are using an Agile Scrum framework, your daily standup meetings are well supported by using custom views. You can create your own custom views to discuss only the relevant issues of the tasks. This feature is time saving and efficient for a daily ten minutes standup. The other new features that make Jira a must buy are due dates notification, assignment allocation, labels, assigning priority levels to tasks, and developing epic links which displays the user story and the project progress. For Kanban framework users, Jira provides Kanban boards where you can turn on and off features that you want to display or hide from other members. Jira provides high flexibility with features that maintain the tasks and deliverable backlogs and these features are applicable to different frameworks. Sprint planning, releasing sprint, and organizing history is very organized in Jira. It can be used for any type of project management. Customer support is available for Jira, which is very helpful.

Jira has deficiencies on micro level. For a particular task, if you are maintaining the workflow, it is hard to customize the columns. Jira always displays all columns on a single view, more like a static view without scrolling. This leads to columns being smaller in width with smaller font size text, which sometimes become hard to read. Unavailability of scrolling leads to column being fit in a single screen browser. Pricing is also an issue. Jira is expensive and fits very well in the budget of big enterprises, but many for small sized firms it is a hard pass. Also, limited user excess to Jira makes it challenging to most small size companies. There is a trade off between ease of use and efficiencies. User has to have good knowledge of Jira navigation and customization before he can make the project management efficient. Customer support is helpful, but comes at an added price. Overall, customization, ease of use, and price are the biggest drawback for Jira right now.

Extensibility. Jira really can be all things to all users. There are so many business workflow processes that we have implemented and all in Jira: advanced software development, workflows for processing contracts and invoices, and support work with incidents and service requests with approvals.

Lastly, with the large dev community and a large pool of app add-ons, we are confident we could extend Jira to be what we need it to be.

If you don't understand the principles of Agile software development, there will be parts of using Jira that will be foreign to you and will likely go unused.

There is a steep learning curve on the administration-side. With so many functions and features, it can be difficult to know all of your options. The "schemes" that power the project administration can also make it difficult to troubleshoot your setup.

1. As a member of a Scrum team, I use JIRA by atlassian everyday and it makes it easy to collaborate.
2. JIRA by atlassian makes team collaboration easy especially when we are working on a common project.
3. One more think I like about JIRA is that it makes tracking my team's work flow easy like ABC
4. JIRA by atlassian is affordable compared to competitors in the same industry.

The customer support is not very responsive. I wish they would improve their customer support services.

It's a very powerful tool. It provides many advanced features to collaborate with people. We can easily tracks things on Jira through our mobile devises and other gadgets. It helps us to plan the projects with tasks and sub-tasks.

It is an expensive software compared to other open source software. I have worked with many software Jira is one of the most expensive product that we have used in our projects.

1) Integrate seamlessly with development tools like Slack, Github, or Bitbucket.
2) Workspace is very configurable; you may customize the components of each task on your board, as well
as create your own icons, labels, and automated processes.
3) Connect all issues/tasks to Epics and view the anticipated outcomes in the Product Roadmap.
4) It offers the flexibility of a kanban board, which provides the user with a clearer view of what has been accomplished, what is in process, and what remains.
5) User story statuses may be used to monitor progress and control workflows.
6) Allows for bulk import of epics and user stories, which speeds up administrative duties if this information was previously recorded in another format, such as CSV.

1) Only internal users may be allocated to tasks and user stories. This might result in unnecessarily long delays when external users want immediate input or participation.
2) When many boards exist within a project, statuses (user stories) cannot be established explicitly for each board.
3) User stories may be assigned to just two categories of users: assignees and reporters. JIRA does not permit the assignment of numerous assignees to a single user story.

Jira is a nice and powerful tool to track our projects. This includes all Epics, Stories, Tasks, Sub-tasks and bugs. It allows for many options as well, including labels, easy prioritization (drag and drop). Recently they have added features to help track milestones, so you don't need MS project anymore. There are a lot of different reports (good for clients) and numerous integrations available.

After you get to so many users, the costs increase quite a bit. Confluence and some add-ons are also additional costs. We have also found the odd bug. For example, the wrong ticket is updated, or in the backlog view the mouse curser can no longer select rows (fixed by a refresh). Classic Projects vs. New Project is also a bit confusing. It's hard to get new features for some of our old projects, unless we recreate the Project from the start.

One of its strengths is its flexibility and customization. Jira allows teams to create and track issues, assign tasks, set priorities, and monitor progress through various workflows and dashboards.Another advantage of Jira is its integration with other tools and platforms. Jira can integrate with tools like GitHub, Bitbucket, Confluence, and many others, which makes it easier for teams to manage their projects and collaborate seamlessly.

One of the main criticisms of Jira is its complexity. Jira has many features and customization options, which can be overwhelming for new users. It can take some time to learn how to use Jira effectively and configure it to suit your team's needs.Another potential challenge with Jira is its pricing. While Jira offers a free version for small teams, its pricing can be relatively high for larger organizations or teams with more complex needs. Some users may find it difficult to justify the cost of Jira compared to other project management tools.

The best part about JIRA is the ability to keep track of all work being done via tickets. I love that JIRA works for all kinds of styles of work. We work within an Agile environment, with some teams using Scrum and other teams using Kanban. No matter how the team is structured, they utilize JIRA tickets. This is great because there is a single repository for all work being done and we can easily search for tickets across all the different teams. The use of Epics vs. Stories is very easy too. We can keep track of what tickets belong to which effort with ease and show the progress of work through the tickets. We can also easily maintain a backlog of tickets. If two separate people submit a similar ticket (or at least two tickets that reference the same work effort), we can combine those tickets easily so that we aren't feeling overwhelmed with more tickets than actual work.

The biggest debate among our team members is when it is necessary to create a ticket. JIRA has created a culture of needing to log every little thing, even if it takes just a moment to complete the work. Sometimes, it takes longer to create the ticket than to complete the task at hand. That tells me there is too much reliance on JIRA to report work completed. It causes some in management to show that their department is succeeding simply by the number of tickets completed. But the tickets don't tell the whole story, especially because there isn't a time component to those tickets being completed.

Jira is the great tool when comes to administratering the custom workflows. We were able to define and automate most of the workflows tasks thus reducing lots repetitive manual efforts. As an administration, we have so much of knowledge base available from Attlassian. Out of the box, we get generic yet useful workflows and features which can onboard most of the software and agile projects instantly.

Able to import and export workflows from one instance to another Jira instance is missing.

My organisation uses Agile software development to do product development, it would be appropriate for me to say every one of us uses this software right from the developers, to QAs to designers to Product Managers to even the senior management. Everyone has their own work areas inside JIRA. It is difficult to say in few words what JIRA is, it is a complete suite for a software development company and I'd suggest you try out JIRA no matter the size of your team. My main work areas and familiarity are the backlog, story management and issue reporting. JIRA acts as the single source of truth with its easy to use Epic and Story feature which makes the life of a product owner very comfortable. The development teams are then able to do their story estimations and sprint planning all in the same place. I would highly recommend you to try JIRA even if you are a startup or a big software house.

JIRA has a learning curve (at least for me, coming from a non-technical or project management background) but with a bit of training (can be done by yourself) it is not that hard to get up and running. Initially, I struggled to find my way around the software and also didn't know how to use some features and tools. But when you get accustomed to the UI, you will realise the power of JIRA.

First of all, this product offered a free trial to experience the features first-hand without any strings attached. It was great to have the ability to go and play in a sandbox environment and carefully evaluate what it can and cannot do for me and how it can add value to my organization. Set up and gaining access was easy and quick. The different permissioning levels make sense to stay organized and maintain accurate information. Some of the features I liked the most was having a great UI for exploring and learning without much training. I was personally tasked with setting up a couple of projects and the respective boards for my teams and I was able to do that in a pretty self-serve way. The design is minimalistic and doesn't feel overwhelming, it is clean and navigable. Easily creating backlogs, sprints and administering those are also my favorite features because it makes it so easy to implement an Agile project management and software development culture. The categories of initiatives, epics, stories, tasks etc. align very well with the Agile methodologies in following the same hierarchy. I love being able to get a quick summary view of the tasks before diving deep into the details. Assigning owners, labeling, story points to track work effort needed, description fields, attachments, comments and seamless integrations with other products make it all the more user-friendly. Kanban Board views in Active Sprints tabs provides a clearly easy to understand view of progress.

Managing boards within each project is the first that comes to mind. Jira does not offer a standard naming convention for the projects and boards and this can cause some major confusion. I have hard coding this manually and training people to do the same to ensure consistency. If you attached Lucidchart diagrams or embed other important document within tasks or epics, they don't update in real-time or even with refresh which is frustrating. This runs the risk of people getting outdated information which can misinform their actions. The search functionality within Jira is also something that I like the least. It does not return optimal results or even close to optimal results. Sometimes it does not search for metadata and you have to remember the actual word you're searching for to track down a task. It returns an overwhelming amount of results and the filtering or sorting options available are confusing and hard to understand. Another limitation is that even though one project can have multiple boards within, it can only have the one same backlog of items which does not make sense to me. There also cannot be multiple sprints running across different boards and all of this makes me wonder what the actual difference between projects and boards are. Jira also lacks some automation in moving tasks to different statuses upon completion. The workflows are suboptimal and don't work as intended most times. The reporting capabilities within Jira are also quite weak in my opinion.