Jira reviews

Het fijne aan de software is dat je een prima overzicht hebt van de taken die er aan jouw profiel hangen. Je kunt hierdoor makkelijk prioriteiten stellen. Daarnaast is het fijn dat je met meerdere tegelijkertijd in een project kunt werken en altijd de laatste bestanden kunt gebruiken zodat iedereen altijd met hetzelfde bestand kan werken.

Het dashboard op de homepage komt wel wat rommelig over. Je moet goed kijken wat er in welke kolom staat.

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

It is very convenient for me to open and manage every task assigned to me or my team, as well as the numerous expectations everyone usually has. It is quite easy to manage and comprehensively document every change’s history and lets us assign roles to various individuals.

This one has its learning process that take time, and it cannot be used offline. This can be summarized by saying that the batch ticket moving feature is not available.

A proper organized tool for developers and team.
Good UI platform will all the information related to the issue either in past or present can check in one place.

A lot of basic features needed third party paid plugins.
Customer support is very less interactive as per the users using JIRA.

1) Releases/Versions:
Releases allow us to work in parallel on multiple efforts with the same team.
2) Parallel Sprints:
Same as releases, we are a lean team and we have to work on Product features and polish/bug fixes simultaneously.
3) Custom Filters: I like these the most!

They have taken out small pieces of functionality and made them separate products. These products are now paid and for those small pieces of functionality, you have to make extra purchases. e.g. Pages

We use JIRA online and it's dead simple to create and manage complex tasks. I love the ability to integrate with great packages like Confluence (which is SOOOO much better than Slack!).

Getting new employees up to speed on using the software is more time consuming that it should be. I'd prefer a more intuitive UI.

Jira has a strong SaaS-based offering that makes the administration and operation of the product simple and easy. The software has multiple options for viewing tasks (from project-task style to Kanban style) which allows different teams to be flexible and use different formats.

The difficulty of running the hosted version of the software with custom plugins is almost unacceptable for enterprise-grade software. The concept that enterprise project-management software requires dedicated IT assets to service and maintenance increases the overhead of the software to unacceptable levels. If a deployment requires a host, non-SaaS version of the software with custom plugins, reconsider.

Jira is the most professional ticketing solution I found so far. It is by far the easiest to use and is the golden industry standard.

Some options related to sprints can be hard to find in the context menus, but once you know where they are it becomes much easier to use.

- Jira has the most critical features that every small to enterprise companies use to manage project management, application development, time tracking, workflow automation for various business use-cases, integrations with external applications like Copado (CI/CD) tool for Salesforce
- Jira has very important usage in our company. All the teams uses Jira to manage all the deliverables and for tracking project management, feature releases, etc.

- The pricing of jira can be cheaper when compared to other alternate solutions available in the market
- The support of Jira can be more available in all times to resolve critical issues
- The UI can be more customized to better fit every customer needs without lot of overhead time

Its interface which gives a better look for team, whether defects are resolved or we can implement shift left strategy with charts provided. Sprints are easily executed from start to end and also Kanban is implemented with push and pull. SAFE can easily be implemented using this tool. It has good work log management and assigning task, where you can create sub task. Epic, theme, Task, SubTask Milestone can be created and tracked easily.

Documentation part is only maintained when everyone follows standard method of maintaining updated comments, in Sprints the scrum master has to remind for comments always. Chat History can not be added to the Jira, its only through conversation things can be tracked. Naming conventions like tagging is not shown for issue or defect to find and link to past issues

The user interface of JIRA is often praised for its user-friendliness and intuitiveness, making it easy for both technical and non-technical users to navigate and utilize its features effectively. Furthermore, JIRA offers extensive customization options, allowing users to tailor the tool to their specific needs and preferences.

Setting up the workflow and advance reporting features is complex. However, it is worth the time. If documentation and tutorials get better, it would be great. The application provides advanced reporting and analytics capabilities, empowering teams to gain insights into their project metrics, track performance, and make data-driven decisions. JIRA also facilitates seamless collaboration among team members, with features like comment threads, activity streams, and notifications, ensuring everyone stays informed and engaged.

Jira helps team discover agile foundations with the guide of a scrum master or project leader. The sprints provide guardrails to teams take smaller chunks of work. Jira provides a centralized location to work in and can reduce the amount of communication gaps.

The greatest opportunity Jira has is that the user experience is rough in the fact that the product needs in-depth training to properly use it. For example, there aren't any youtube tutorials or best practices documents on why the end user would use label or a component. Most project leaders I know do not have a standardization why they use that and it causes confusion on project teams. The product isn't a plug and play, it is more that any user will need several lessons on simple actions such as creating a story, creating a Jira board, and creating Jira JQL. At the end of the day, there is a steep learning curve for this product and that increases the resistance for enterprise teams to go agile.

With Jira we do not need to worry about making a personalized configuration, since we have multiple templates and this is vital to start quick and reliable planning.
It takes care of the basic configuration and then we can assign resources, customize roles and privileges, and make sure people see what they need.
Another incredible advantage is its mobile APP that guarantees monitoring outside the organization and allows us to always stay connected.

Jira allows us to start with an unlicensed model to carry out tests and ensure that its use is what we really need, but after that we must consider that the licensed version is necessary for constant growth in our organization, so it is also important to consider the number of users that we are going to have to license for a successful implementation, and if we can afford it, we will have an excellent platform in our organization.

I work for a large clothing retailer that often runs promotional coupons and sends out emails to customers. JIRA houses all of the collaboration for our company in creating and testing these promos and emails. What I like is that everyone, from the communications team to the Quality Assurance Team to the IT troubleshooting team can be in one place to resolve issues quickly.

I love that there is the ability to tag other users and quickly get attention to issues that need a fast turnaround (emails and promos are often made within 48 hours from creation to launch). I also really like attaching 'sub-tasks' to a main project; This keeps organization a priority without having to search for every related task associated with a project. Related to this is the ability to attach documents right to any project/task for easy download.

You can save searches and filters to your home page. For example, I have a filter for viewing only email projects, and another for promotional information. Once you get results, you can sort by title, date updated and a few other categories.

At first glance, the layout is a bit overwhelming. You have a giant list of projects, and the search doesn't always bring up what you are looking for. It takes a bit of time to learn how to navigate. I would probably like to see 'tags,' or additional ways to categorize a project so that you can search for it through a few more parameters. For my needs, this isn't too important because of the short lifespan of emails and promos. But I could see other applications needing something like that.

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.

Jira is *incredibly* versatile. You can customize almost every aspect of your Cloud instance, Project, Boards, & Workflows to fit nearly any use case, and across multiple departments.
Permissions to your Jira instance can be restricted at a very granular level if need-be, but can be more broad if the occasion calls for it.
Additionally, and probably the largest reason we transitioned from enterprise Jira to a Cloud Jira instance is the pervasive availability of integration across the market.
Speaking of market - Jira has a growing 3rd-party market that offers enhancements to the Jira platform that Jira does not natively provide or are too complex for an untrained Jira administrator to script themselves. Of those that are "approved" by Jira, we are extremely happy with the breadth of functionality, integration and ease of use.
With all that I do have to say that our favorite thing with all project leads is Jira Automation. Once you understand the "SmartValues" language that automation runs on, the use cases for automation are truly endless. It is one of the many strong features from a project management perspective.

Jira takes a village. Atlassian has an incredible resources in the "Atlassian Community" and they do a great job of having experienced users there to answer questions but, because each instance can be set up so differently, the actual customer support request portal is limited to bug fixes. As a result, much of my time administering Jira is spent researching how to fix a roadblock or how to modify permissions - a lot of "learning by doing". Generally speaking, Jira can be difficult to use from an administration perspective, *but* for the purposes of moving ticket along, the UX is pretty good and the UI is fairly intuitive.