What advice do you have for others considering Jira?

I would rate the customer support a 10 on a scale of 1 to 10. You may work with Jira only if you have enough internal resources to automate it and to build your own processes and flows because it's very flexible, but default templates might not be as effective as you expect since they're pretty much average. But if you have an internal development team and resources for supporting Jira, I think it's the best solution. On a scale of 1-10, I rate Jira a 9.

I can definitely recommend Jira to those people who are planning to use it. On a scale of 1-10, I rate Jira an 8.

If anyone needs a project management tool, I would definitely recommend Jira based on my experience. However, the specific functionalities you can use might depend on the role-based access and permissions within the organization.

For smaller organizations, it might be better to consider alternatives like Linear.io. But if you need an integrated system, especially with other Atlassian products, Jira is a solid choice. It is widely used, so the transition is easier if someone moves from one organization to another that also uses it. Additionally, its automation features are powerful and can address many use cases. The reports are useful, giving an overview of a sprint's progress and indicating areas for improvement. However, I have yet to use the analytics feature much. I rate it a seven out of ten.

I would advise people to use Jira. There are other open-source products available that individuals can consider first, depending on the company's budget. Jira is a fairly stable product, but there are other open-source solutions worth exploring. Overall, I rate the solution a seven out of ten.

From a project management perspective, my project manager assigned some Jira tickets, and I started to do it on a weekly and daily basis. I send a request to a Jira ticket to open it, and during the process, I start describing how I am replicating that issue, explaining it in that Jira ticket. After that, I resolved that Jira ticket put that Git code in the expression part, and submitted it. Regarding reporting and analytics features, my company uses Jira for software development projects as if it were a single tool. My company uses the tool in a manner where we send requests to one developer, and they open a Jira ticket using the email. Every day, they update so that everybody is able to see it without any description, while my team can see what the developer is doing daily. If a developer is updating, everybody can see that in the company. The tool is very easy to use, and it is easy to understand areas like script planning, story points, and backlog grooming. I recommend the product to those who plan to use it. I worked with two scrum tools. In Azure also, my company uses scrum, which is a little bit uncomfortable for me, but I am very comfortable with Jira, a major reason I suggest it to other people. I rate the overall tool a nine out of ten.

The decision to use Jira on-premise instead of the cloud is primarily driven by security concerns, especially in industries like defense, where sensitive information must be protected. We want to continue using the tool, but we may have to explore other options due to the lack of on-premise support and Atlassian's emphasis on cloud deployment. If it extends its support for on-premise usage in closed network environments, we would gladly continue using it, considering our current investment and experience with the platform. However, if no such support is provided, we may need to evaluate alternative solutions that can be deployed on-premise. I recommend using Jira because it's easy to work with and open, allowing for integration and development of additional features if needed. Its ecosystem is vast, with a large community worldwide using Jira, and it offers many add-on products for various needs. I rate the overall product an eight out of ten.

Jira is easy to use and maintain; everything is in one place. Minimal maintenance is also required. We have our developers to maintain Jira. They will develop whatever we require for labels and provide them to us. If you want to inform me about the adaptations for scaling Jira, it will be convenient to use Jira, but most of the reports will be easy to generate. We integrate with Git, making the process a bit easier. Overall, I rate the solution a ten out of ten.

Overall, I rate the solution a 10 out of 10.

Overall, I would rate the solution a nine out of ten. I would recommend using this solution. Go for it!

I haven't used a lot of direct integration with Jira. I've seen it used with code repositories for continuous integration and continuous deployment. It's really fast. Everything is automated and very easy to set up. I haven't used all of the features. I would definitely recommend Jira. My advice is to use the online resources on the Jira home page. There are a lot of people who will help you set it up for free. We can avoid making a lot of mistakes by using the community advice. Overall, I rate the solution a nine out of ten.

I rate the product a nine out of ten overall.

Use all the reports which are generated. You have to make a system for the process. Here is a small example during a subtask. The time input via the source is not mandatory. But you have to make it mandatory either from the back end. You’ll not be able to fetch the reports on the performance, the health of the project, capacity management, or IT management if the data is not input properly. So this is something which people most people don’t take care of as a Jira planning. But when you plan a project, you have to plan these things. I rate the overall solution a seven out of ten.

I'd recommend it to others. Overall, I'd rate it an eight out of ten.

I'm coming from an Azure DevOps background, and we use the integration board. It is very easy because the source code is there under one umbrella; however, Jira is not under the Azure DevOps umbrella. If your company is using Azure DevOps or Git as a repository, I recommend using the Azure DevOps board rather than Jira. I would rate Jira at seven on a scale from one to ten.

I would rate Jira an eight out of ten.

I have not had a lot of time to explore the solution. My rating might be higher if I had used it more. I rate Jira a three out of five.

I would rate this solution an eight out of ten.

I would advise others that Jira is a good solution and I would recommend it. I rate Jira a nine out of ten.

I would recommend the solution to others. I have been happy with Jira. I rate Jira a seven out of ten.

I rate Jira eight out of 10. It boosts productivity tremendously by eliminating the chaos between development and QA. Jira manages the entire pipeline from development to production. If you're thinking about implementing Jira, you should go for it. It will make your life better by streamlining the tedious daily work of project management.

I rate Jira nine out of 10.

I would recommend Jira to others. I would advise others to be sure to do the reports correctly because there can be some challenges in reporting and in the testing phase. I rate Jira an eight out of ten.

I would recommend this solution to others if they cannot find a better one. If someone wants to implement Jira, then it should be fully transitioned. In the beginning for us, it was not implemented one hundred percent, which caused some hassles for the transition for everyone. We have benefited from the use of Jira has improved the way we operate. You can see what everyone is doing in your team and you can check and get updates on progress. I rate Jira a seven out of ten.

My advice to others thinking about implementing Jira is if you only want it for the standard flows and use it as an issue tracker in a software development setting, it is a good solution. We are using the online version. If you are in need of changing workflows or appearance, fields, screens, et cetera, Jira is not able to do this well or it's not possible at all. Jira has found its place in our organization and it does those tasks. They should focus on speed and stability, and in that order. It's excellent with regards to preexisting integrations but it is poor at configurability. Whether Jira is a good solution for you depends on your use case. From what I have seen creating different workflows in Jira is not good. I rate Jira a five out of five.

I would rate this solution an eight out of ten.

I rate Jira an eight out of ten.

I would advise having proper planning because you don't want to clutter your Jira. Without proper planning, you would go on creating a lot of labels and other things, which would be of no use. You need to do release planning and then accommodate things into Jira. A lot of companies have a separate release planning team, and then there is a separate Jira infrastructure team. All these teams should think and work together. Otherwise, everybody would be creating their own tags, which won't make sense. I might create a tag for daily bugs, and someone might create another tag for the same thing, which would result in cluttering. I would rate it an eight out of 10. Jira is an amazing tool. There is no doubt about it. We have no thoughts of using any other tool.

We are just customers and end-users. I'd rate the solution at a nine out of ten. There's always room for improvement, however, it's a very good solution. I would recommend the solution to others.

Jira offers Agile project methodology management and can be used for defect tracking and bug tracking. I would strongly recommend any organization wanting to use Jira, to work with the Jira team to understand what each product offers and how suitable it is for their organization. The Jira team could be consulted to understand the project, your department's requirements, and provide a proper way of managing the tool and advising what are the kind of roles you'll need. I would rate it an eight out of ten.

I would rate this solution 9 out of 10. The only thing that I'd like to advise is to just monitor the market and keep an eye on comparison between the Jira and ClickUp.

From a user perspective, Jira is simple to understand if they use its data functionality. If you want to extend it to custom feeds then you need further education. If you are considering Jira, take a look at the online versioning and online pricing. I would rate Jira an 8 out of 10.

I would recommend that an organization implementing Jira ensure that someone gets training both at the developer level and the project manager level. The developer needs to know what needs to be done, what are the components and why are they there. The project manager should join the training and determine if there is a relation between multiple projects to see that they are really integrated well into other components of continuous integration and continuous delivery. Because of the slowness, I would rate Jira an eight out of ten.

When we cut over to Agile, it was a huge task to get everybody on the same page in terms of the setup and rollout. When we looked at each other's desktops, it looked so different, and our central team did a lot of effort in making it all look the same. I saw the full central team being pulled forward to resolve these inconsistencies. It is so open that it allows inconsistency. So, you need to have a very strong and resourced team for the initial setup, implementation, and training. Otherwise, it can just fail. It could be a good thing that it is open, and everybody can have their own Jira, but finally, when the organization wants some statistics on what's happening at the enterprise level, you will not get any data. So, my suggestion to anyone cutting over to Jira is to have a very strong and resourced team centrally. You should roll out, learn, and come back to it. You should repeat this process and keep on learning and coming back. It has to be a very strong cycle. I would rate it an eight out of 10.

I rate this solution an eight out of ten. I think it's much better than other competitors' products.

I would tell potential users that they should all get it. On a scale from one to ten, I would give Jira an eight.

We are a customer and an end-user. We use Jira for internal projects. I'm a Java architect. I'd rate the solution at a ten out of ten. I'm very satisfied with its capabilities.

I have found the cloud deployment better than the on-premise. However, for those wanting to implement this solution, I would advise them to compare the pros and cons of each before making their selection. I rate Jira a ten out of ten.

It is easy to use and easy to onboard. It has got a good foundation of offerings for the business requirements if you're working on an agile project or user stories. I would rate Jira a seven out of 10.

The product is very useful. As a program manager, I recommend it wholeheartedly. The cloud version is easy to set up, and there's no maintenance required. I haven't incurred any issues with performance or updates being applied incorrectly or any bugs. I rate the solution nine out of 10.

I don't know what to compare it to. It is not an A product, but it's a strong piece. I would rate Jira an eight out of ten.

It has a lot going on. They own Bamboo, but right now, we're using Jenkins. I have used Azure DevOps at another company. I would advise going for Azure DevOps because it has everything. You've got your DevOps, and you have your Repos. Everything is integrated. I would rate Jira a six out of 10.

I would advise those wanting to implement this solution to contact an expert. This solution is a top-of-the-line CRM, I have used the others solutions, and it has the most flexibility and the best visibility. I rate Jira a nine out of ten.

I'm a customer and an end-user. I would rate the solution at an eight out of ten. For the most part, we have been satisfied with its capabilities. I would recommend the solution, however, I would warn that likely a company will also need to add many plugins in order to get the solution to do what they need it to.

I'm not sure which version of the solution we're using currently. I'm a customer and an end-user. I'd advise users considering the solution to make sure that they have a little time to review it and understand the tool and make sure they actually find that it is a good solution to meet their needs and that it's what they're looking for. From Agile delivery teams that are here to deliver their MVPs and stuff like that, I think it's great to keep track of all their backlogs and stuff like that. It is also great for someone from a use case perspective as they break it down well. I'd rate the solution at an eight out of ten. Of course, I'm still learning it. That said, it's great for keeping track of all the items and the stuff that needs to be done and for the use cases that have been closed, to make sure that we get the proper sign-off and understand the line of business.

I would rate Jira a five out of ten.

I would rate Jira at eight on a scale from one to ten.

We are just customers and end-users. As we are using the cloud version of the solution, we are always on the most up-to-date version. For simple project management, Jira is too much. If you want to manage a project precisely, however, then I can recommend Jira. It's not only a software-specific version. There are different versions of Jira so that you can apply it to different areas - not just software. That is one good aspect. I'd say that it is very polished, and has a very well-defined approach to project management. I'd rate the solution at a nine out of ten. We've mostly been happy with how it's worked for us.

I would recommend this solution. I would rate Jira an eight out of 10. It is definitely not perfect, but it is almost perfect.

Our team does not use the solution exclusively. There are multiple ones which do, although I cannot state how many teams are doing so. I do know that the entire section of our agency is doing so and this accounts for a lot of people, well over a hundred. The solution is pretty good and is geared towards those with multiple teams who are using it for the same purposes as us. We use it for providing daily and scrub updates, for which it is really good, as it allows one to track every entry and see when it's entered, timestamp and all. So, if a person has a lot of mission-critical or time-sensitive activities, JIRA is pretty good for tracking and helping to keep everything organized. While I am still biased towards services at the moment, I rate Jira as an eight out of ten, at it is really good and very functional.

I rate this solution an eight out of 10.

I would definitely recommend this product because it's scalable and easy to use. They provide best practice articles and quick start tutorials which are very helpful. If a new user has all the documentation, they can go from zero to hero very quickly. I rate this solution a 10 out of 10.

Overall, this is a very good product and I think that it is the best project management tool. It is used company-wide and I recommend it. I would rate this solution a nine out of ten.

This is definitely a tool that I would recommend to people, depending on their needs. In summary, it is a good product and the only room for improvement that I can see is that it needs better integration. I would rate this solution an eight out of ten.

I would 100% recommend this solution to others. We plan to keep using it. I would rate Jira a nine out of ten.

I'm just a customer and an end-user. I don't have a business relationship with Jira. It's my understanding that we are using the latest version of the solution, however, I am not 100% positive that is the case. I don't know the version number off-hand. I am also not sure which deployment model we are using and if it is deployed on cloud or on-premises. I'd recommend the solution to other organizations. I would rate the solution at an eight out of ten overall.

I would advise others wanting to purchase the solution that they can improve their business UX. This solution has been established in the market and is commonly used in many project management sectors because it can be easily used once you have experience. If you are new to this solution it could be confusing to some people because there is not a proper project flow. For example, Once you create a ticket or any task, you are not able to see what you just created in the notification area. Currently, you receive a pop-up and it will go off after some time, if you do not click the pop-up when it comes up you will have to refresh, go back to the project, and then find out the task from there. This could be simplified in the future. They provide a product that is very good but in terms of a presentation, they have room to improve. I rate Jira a nine out of ten.

The most important thing is to precisely decide your flows and different stages and cycles. If all these are very clear, you won't have a problem setting up Jira. I would rate Jira a nine out of ten.

We are a customer and end-user of the product. I would highly recommend not using this product if your focus is software development. Organizations should seriously consider alternatives such as Azure DevOps or TFS, which are more focused on modern interfaces and more accurately modeled to modern workflows. I'd rate the solution at about a three out of ten. It doesn't really offer a whole lot that's actually usable from a software development context beyond extremely simple and free alternatives.

We are just a JIRA customer and an end-user. We are using the latest version of the solution. I'm not exactly sure of the version number. We do not plan to switch to another solution. We're quite happy with this product overall. I would rate the solution at an eight out of ten.

It is a well-crafted product. I don't have any concerns. I would rate Jira an eight out of ten.

On a scale of one to ten, I would give Jira a seven. To be a ten, there should be more options where you just click and drag. That would be nice. It's hard to copy and paste requirements. You lose your formatting and everything. So just simple navigation stuff should be improved.

I would rate this solution an eight out of 10.

I think the technical support and the customization of the line of business are the most important points for me as a BA. I don't think the license for a business is low. We think - so far so good. On a scale of one to ten, I would give Jira an eight out of 10. Nothing is perfect.

I would definitely recommend Jira for project management and similar uses, as well as other products from Atlassian like Bamboo. Jira isn't what you would call a "coded solution" for scrum or anything like that, but it's able to do a lot of different things for people who are looking for that kind of thing. If you are looking for a custom-made solution specifically for agile or scrum, then you can go try other products like Valley or others. But if you want a good general-purpose project management system with solid integration solutions like Bamboo, then I think Jira is the product for you. I would rate Jira an eight out of ten.

I would recommend this product to others. I rate Jire a nine out of ten.

We're just customers and end-users. We don't have a specific business relationship with Jira. I'm not sure of which version of the solution we're using currently. It's my understanding that it is the latest version. I'm not sure if we are using the cloud or the on-premises deployment version. Currently, I'm more focused on the Micro Focus product as opposed to Jira. That's more where my expertise is at the moment. That said, it's pretty easy to use and I would recommend Jira to other organizations for that reason. Overall, I would rate it at a seven out of ten.

Depending on the use cases, I would either recommend Jira or not. I would rate this solution a six out of ten.

To a certain extent, maybe 70% to 80%, Jira will meet your project development budget. It has integrations with other platforms, so if you want to put it in your DevOps continuous integration flow, it can be done. If you're engaging in software development, there should be a single repository where you store everything. Then you can start managing it with Jira based on the business requirements and the user stories. On a scale from one to ten, I would give Jira a seven.

I use the current version of the solution. Right now, I'm on the free version. I'm just trying it out right now, to see if I like it. I would recommend the solution to other organizations. Overall, I would rate it at a seven out of ten.

We're just a customer. We don't have a business relationship with Jira. I'm not sure of which version of the solution we are using. I'd recommend others go ahead and try the trial version of the product. If, after that, it seems to fit your needs, a company should go ahead and implement it fully. Overall, I would rate the solution nine out of ten.

I would recommend this solution. We are interested in migrating to Jira and using it as our internal tool for agile projects and for controlling the IT software development cycle for projects like consulting or API. It will be more used for agile projects. It is a good tool. We also have the latest version of Microsoft Teams, but it is limited. It is better to use Jira. I would rate Jira a nine out of ten.

It is essential to track efforts right from the beginning of the project i.e the from the day of planning and incubation to delivery and deployment.

It is an excellent tool to summarize and get our stacks of data into a platform for operational overview and interface tracking. It is very useful for us. I would rate JIRA a nine out of ten. Not a ten because of the GUI pie chart. The beauty of the dashboard is not perfect, so I subtracted some points.

We're just a customer. We don't have a business relationship with Jira. We're using the latest version minus one, due to the fact that it was installed year. That upgrade was last year and it is my understanding that there is another version coming up. I'd recommend this solution to other companies. The product is very scalable and it's very flexible to match any organization, however, the trick to using Jira effectively is that there should be a business process documented in place before using it straight. The mistake that many people do is they consider the tool as the base and they configure their processes according to this. If they work the other way around and have a great process between all cycles, and then implement that process on Jira, it's very beneficial. Overall, I would rate the solution eight out of ten.

Have a training session before you begin using it. That tool is good for teamwork, but it doesn't replace a face-to-face discussion. Among yourselves and your teams, establish some conventions as to how you will describe your tasks — what criteria will be acceptable? Include a section for requirements, have a section dedicated to discovering your setup because the tool has its limits. It helps you organize your work, but it doesn't replace the self-discipline of the developers to stick to some team conventions — that's also really helpful to get the full benefits of that tool. One of the main advantages is that everything becomes visible when you use this tool. When your work is done in full daylight, it's difficult at the beginning because you feel like everybody's looking at what you do — it's all visible. They can access the information through JIRA, but at the same time, you're not going to get stuck too long in your corner. The drawback is that you feel more like you are being spied on. It feels like you're working in an aquarium. Everything you do is visible. But at the same time, you're not going to get stuck on your own. Without this tool, it's easy to get stuck on your own. There's room for improvement. Sometimes the window is too crowded and the integration capabilities need to be improved. Overall, on a scale from one to ten, I would give Jira a rating of eight.

While I'm new to the company, it's my understanding that it is a partner of Atlassian. We use the latest version of the solution, as we use the cloud, which updates automatically. Our company has both Azure DevOps and Jira. I use Jira, and Azure DevOps is used for other purposes. Most projects, all projects that are using Azure DevOps are legacy projects. The new projects and new solutions are using Jira. On a scale from one to ten, I'd rate Jira at a ten. It's a very good product. Both tools, Azure DevOps and Jira are at the same level. In terms of preference, I typically choose Azure DevOps for familiarity but not for features. For features, both are the same. For example, Jira has amazing features that Azure DevOps doesn't have, and also Azure DevOps has the flexibility that I like very much. Both tools have different interesting aspects. However, if Atlassian would implement traceability, I would prefer to use Atlassian. For me, it's more complete and allows for smaller teams than Azure DevOps.

I would highly recommend Jira to other interested companies. On a scale from one to ten, I would give Jira a rating of eight.

I would guess we are using the latest version of the solution as we're using the cloud solution. I'm guessing that it's continuously updated automatically. I'd advise others to consider the solution. However, It depends on what they're trying to achieve. There are a lot of easier project management tools like Monday.com, for instance. It's a lot easier to get up and running. If your vision is to become a larger software development company, monday.com might be something that is usable for project managers. However, it wouldn't be a good tool, at least how I've seen it, to connect everything together as we're able to do in the JIRA cloud with all the connecting apps. I would guess we would be able to integrate Monday to JIRA or something like that. It's really easy to get JIRA connected to Confluence and Bitbucket and to have the service desk as well. That way, everything is in one place. Again, it depends, on based on where you're heading. If the company is looking for easy project management, there's a lot of tools that would be just as good as the JIRA. If you're looking to distributing the teams and connecting a whole ecosystem, then definitely JIRA is a good pick. I'd rate the solution seven out of ten.

I would recommend this solution to others who are interested in using Jira because you can do a lot with it. However, I think that as you start working, you should start small. Work with it and try to configure things that you really need. Involve the whole team in what you are going to use and how you're going to use it. I would rate Jira an eight out of ten.

We're just a customer. I'd advise, for those users who don't need an enterprise-level environment, that they go for a cloud deployment. For others, they don't really have a choice. They will have to follow up with enterprise security and other protocols. There are not that many options, I would say. I have learned that Jira, starting in 2024, will not be available as a server installation anymore. Soon there won't be any options at all. It will be the cloud or nothing. Overall, I'd rate the solution ten out of ten. It's a very good product. For small teams, the cloud works well. You can do basically whatever you want there, so it's fine. It's also not cost intensive if you're talking about using it for small teams.

We're just customers. My company doesn't have a professional relationship with Jira. I'm not sure which version of the solution we're using. I'm not sure of the last time we updated the solution. I've only been at the company for six months. I'd advise other companies to dedicate two full-time people to learn the solution and train other team members. It's a big learning curve for users. It takes time to get into it. Having dedicated trainers would help onboard people. Overall, I'd rate the solution seven out of ten. If it was more intuitive, and there was less of a learning curve for new users, I'd rate it much higher.

Jira as it is, is a very nice tool. For capacity planning and resourcing, I think it is not built for this and we are trying to make use of it in that area. I would rate Jira a seven out of ten.

I prefer some different practices, like story mapping and inbox mapping or strategy planning. The story mapping is included in all Jira installation. It would be good to see some features for strategy and portfolio handling planning in Jira. I have used Aha! and this tool has a very good framework with a good toolset. The toolset for strategy planning, toolset for portfolio handling, toolset for product handling, and toolset for daily work handling is very good. I think the Aha! team did very good work. I know that this company is an American company and is a competitor for Jira and for some other tools. Unfortunately, I never heard about this tool before and don't know any other company using this tool, but the tool is very impressive. There are a lot of good features. It would be good to see something like that in Jira. I would rate Jira a seven out of ten. I would give it a higher number if the features that I mentioned for the strategy planning would be included in the framework.

My advice for anybody who is considering this solution is to ensure that it meets your requirements. For example, we have been trying to use it for help desk management, but have found that is not well suited for this task. I would rate this solution an eight out of ten.

We are using the latest version of the solution. It's a great piece of software. If you really want to do agile software project management Jira is definitely should be a top choice for you. I'd rate the solution eight out of ten.

This product has steadily improved since the time I started working with it. I would rate this solution an eight out of ten.

It's difficult for me to tell you everything that Jira has to offer when I am still learning. I am trying to educate myself to have a better understanding. I want to learn more. I would rate this solution an eight out of ten.

I would recommend JIRA to somebody considering it. I love working with it. I would rate it a seven out of ten. In the next release, they should make the process easier to be customized.

Jira is an amazing tool, but to get the process streamlined is a challenge. So don't start from Jira. Start with your process first. Agree on the workflow, identify all the stakeholders, and then from there you can go ahead with Jira and implement anything. On a scale of one to ten, I give Jira a 10. Everything already provided is perfect. We are using Jira perfectly for one year now and it's absolutely great.

My advice to anyone thinking about Jira is that it would be wise to at least find out the most crucial functions that you need in the product, what features are most important, determine how the project will use Jira, and the most important thing is to have some kind of user training plan because the tool is so complex and flexible that you can use it in many, many different ways. On a scale of one to ten, I would give Jira a nine. I would give it a nine because of course it needs some improvements. For example, the usability and its speed.

My advice for anybody who is implementing Jira is that it easy to use but you want to understand what your requirements are. You want to know what you want to use it for, and what you want to achieve by using it. With Jira, you get what you input, in terms of your data. For me, I get what I need out of it. I would rate this solution a ten out of ten.

We're just customers. We don't have any type of professional relationship with Jira. We aren't integrators or resellers. I'd rate the solution seven out of ten. I'd rate it higher, however, if the solution wasn't quite so dense and complex. It would be helpful if there were training modules to help teams and users better utilize the full solution. As of right now, we've never really mastered the solution to its full capacity. I'm sure the solution has much more to offer, however, we have only really dug into some basic features. Our organization doesn't really emphasize the usage of the system. I'd recommend those considering using the solution to really get some training before they begin and to maybe try doing some pilot projects to test its capabilities. Jira, as is my understanding, does offer a free trial, and new users would benefit from taking advantage of that.

We're an Atlassian partner. I'm actually using various versions of the solution. I stick with versions seven and eight, mostly. I'd rate the solution seven out of ten.

I'd advise other companies to go for it and try using it. Jira is one of the biggest players in the market. It's a scalable solution and very user-friendly. The onboarding is quite simple. I have never been trained and I've been using it for the four past years. Whenever there is a new release on Jira, we get a guide, which is helpful, and instructions as we use the latest version that comes in the form of pop-ups on your screen. If you want, you can just disregard it, but once you discover them, you can just hover over with your mouse and you can see the new features. If an organization is looking for something that will be easy for its workforce to adapt to, Jira would be a smart choice. With the communication and the bridges that we've established with other tools, it's helping other teams get the information they need without having to get the Jira license or get them to go onto Jira. They just need to find their tool and they get the update from Jira in real-time.

My advice for anybody who is implementing Jira is to install the plugin from Micro Focus because it is a better way to manage the interrelationship between these two tools. Overall, my experience with Jira is pretty good. I would rate this solution a nine out of ten.

I would rate it a five out of ten because it gets the job done.

JIRA, its add-ons, and the Atlassian product world are already very powerful and it is difficult to name significant blank spaces. This is a very powerful solution. Get some advice and training to make the most out of it. You may miss out on some of the capabilities if you don't.

JIRA, its add-ons, and the Atlassian product world are already very powerful and it is difficult to name significant blank spaces. This is a very powerful solution. Get some advice and training to make the most out of it. You may miss out on some of the capabilities if you don't.

My advice for anyone who is implementing this solution is to ensure that your in-house processes are clear. Things have to be clear, as much as flexible, because if it is not correctly configured then it could just be a mess. So, you have to be very clear on what your processes are in-house, and then based on that you can translate them into Jira. Knowing in advance what kind of information you're looking for from Jira will help you in being able to set it up correctly. I would rate this solution an eight out of ten.

My advice for anyone who is implementing this solution is to ensure that your in-house processes are clear. Things have to be clear, as much as flexible, because if it is not correctly configured then it could just be a mess. So, you have to be very clear on what your processes are in-house, and then based on that you can translate them into Jira. Knowing in advance what kind of information you're looking for from Jira will help you in being able to set it up correctly. I would rate this solution an eight out of ten.

It is an excellent tool for project management.

It is an excellent tool for project management.

This software is ideal for tracking problems, managing, planning and carrying out real-time monitoring of the tasks or projects you want to develop in a much simpler way and in the shortest possible time. So I think that if you are looking for a solution that is based on more than the management, this is the indicated choice.

This software is ideal for tracking problems, managing, planning and carrying out real-time monitoring of the tasks or projects you want to develop in a much simpler way and in the shortest possible time. So I think that if you are looking for a solution that is based on more than the management, this is the indicated choice.

It is a user-friendly solution that is simple to use.

My advice to future users is to check out sources like YouTube and look at the main features you want. Potentially with JIRA, particularly with the cloud version, they have a seven day trial. I suggest that future users sign up for the free trial to make sure the features of JIRA meet their personal requirements. Also, the user should make sure that JIRA is a good fit for the user's organization.

Most important criteria when selecting a vendor: * Usability: It should be easy to use. People should not have to undergo a lot of training because it should be intuitive. * It should be scalable and a cloud solution. * It should not be expensive. Cost is a major driver because I work in pre-sales.

I would tell a colleague looking for this type of solution to look at Microsoft TFS and VSTS. Most important criteria when selecting vendor: * A well-known vendor for the software. * A good reputation. * Compare what other companies are using. * The look and feel of the user interface.

Understand your own process: What you are looking for, the size of your company, what your budget is, and the larger plans for the future. There are tools that scale better than others and there are solutions that fit to both small and big teams. There are tools which scale better for larger companies. Most important criteria when evaluating a vendor: * We evaluate the company's strategy. * If they bought an legacy solution to add to the portfolio or if they are developing from scratch. * What are their plans for the future? * What type of support do they have? * What is their business model? * Do they have domestic experience or not? * Are they focusing only on a few customers, and the size of those customers?

It is very capable, but also very complicated. Most important criteria when selecting a vendor: reliability.

I rate it an eight out of 10. It's easy to use. People can become productive with this tool in a short time, and it is really the right solution for an Agile environment. A lot of solutions show very well on paper. When you are selecting a solution, do a proof of concept in the environment.

I'm not the selector of the vendor, but from what I can tell, from what our IT selects, the vendor should be * available for global support, should be accessible in 24 hours, if there's a larger issue * able to collaborate with large enterprises, which sometimes have different cultures, different languages * able to integrate into the existing work environment - we have this tool, and that tool; the tool should fit into our tool landscape * able to provide training. I would rate JIRA a nine out of 10. It's not a 10 because it's inconsistent, sometimes, in how it acts and reacts, like my example with the Epics. But it's a high rating because it's user friendly, it's easy to use, you do not need much training on it. If you know how to work with Scrum, you can easily use it for your own work in a small team. For multiple teams, I'm not sure. I can't judge this because I haven't done this yet.

I would rate it at nine out of 10 because there is always room for improvement, but we love this tool and we use it a lot. I would recommend JIRA. Compare all the tools for bug and task management. After that, you'll see that JIRA is by far the best.

When I am evaluating a product or vendor, I have some intuition about it. I see how the thing is built and works, and I go by my own impression. For me, that is important. And, of course, price and maturity of the product, along with flexibility, are important criteria. I would rate this solution a 10 out of 10. It's an excellent product. It has already improved. It has good support. From the beginning, it was very smart and customizable and built well, works well. There are almost no bugs that I have discovered. It's a good product. I just saw an advertisement on the street for a product called Monday.com. I read a few lines, a few words about it. I hadn't heard of it before that, but I understand it does something similar to JIRA. Obviously, I can recommend using JIRA but if you are searching for something else, the first impression I got from reading the home page of Monday.com was good, so maybe it's worth evaluating.

Learn every module you use (a lot!) before jumping to other modules, like we did, with JIRA Testing and Atlassian Confluence, because the conversation between those modules can be troublesome if you don't know exactly what it wants. The product helps us a lot. It can handle the main features that it's supposed to in a proper manner, so we don't have any frustrations in our daily activities.

JIRA is very good. With another tool, like Confluence, HipChat, Trello, Bitbucket, Bamboo, and FishEye. It creates a robust project and product management process.