We use it to trace our business needs development.
We have some nice dashboards out there where we can track needs for clients or track internal projects.
We use it to trace our business needs development.
We have some nice dashboards out there where we can track needs for clients or track internal projects.
This is our way of communicating with different teams. We are a global company. I am based in San Diego, for example. A lot of the BAs are based in Paris. The development team is based in Minsk. We absolutely need to be in constant communication and on the same page.
With the time differences that we all have, it is very hard to kind of get on a call and centralize the information in person or during meetings. This solution makes it possible.
One of the most valuable aspects of the solution is the fact that everything is traced on one ticket on Jira. We know exactly what has been done and what is left and we share the same feasibility we are assigned. We don't have to wait for team updates or emails or calls or even reminders. We just need to look at the same ticket and we know in real-time exactly what is happening. Without Jira, I don't see how we would be able to manage and trace in a very consistent, effective way. At least, not across all of our development initiatives.
I have never been trained on Jira, to be honest. However, it's easy to navigate. Even for somebody who is never on it, it's very simple to pick up and understand. The only caveat is that when you get a bit more in detail, or you have some business requirements, you don't have documentation that you can just go and consult to enrich your portal or access.
One aspect of Jira that is very nice is that we are able to integrate other tools that our company is using. For example, we do use Salesforce for our support team and that's linked to Jira. Slack, as well, is also integrated into the system. It makes everything so much easier.
Jira has recently updated their UI, but more can be done to make it even better.
One thing that is missing is notifications that we can send out in an automated fashion so that we don't have to log into Jira every single time. We do have dashboards on our navigation pages, but we need to log in to see the current status. I can't just click reports every once in a while to trace or track projects, I have to log in to see. I'd prefer it if the data automatically came to me instead of having to go seek it out.
It's possible the dashboards and the reports are something that can be properly configured on our end. However, I'm not the Jira administrator in our company. I probably just don't know how to do it. Jira may actually be able to trigger these kinds of reports. However, if they don't have this functionality, it should definitely be added.
I have been using the solution for four years now.
We've never experienced any downtime with the app. I can't recall any bugs or glitches. There haven't been any crashes of any sort. It's very reliable.
I would say the solution is pretty scalable. Every single project team in our company uses it. Our staff, our BA, our developers. We do also have DevOps teams using it. Everyone uses it for different purposes. Our company, over the past ten years, grew exponentially. We've tripled our size and we never had any downtime with Jira.
We have business owners, developers, quality testers, business analysts etc. on Jira. We have internal consultants from professional services teams, who trace the needs as well so that they can transmit information to their clients. All the top management personnel go to Jira to consult the dashboards as well. If they wish to trace the progress that their teams are making, they can do so. The solution is basically used in every aspect of the company, and as the company grows, so does the usage.
I've never had to reach out to technical support, so I can't speak to how they are.
When I joined the company, we already had Jira.
I wouldn't consider it complex at all.
I wasn't here at the initial setup of Jira, however, in our company, we have a Jira administrator. Whenever we have a project to review and need to know how it's laid out and how we can place them better, etc, it goes through this person. She analyzes the needs and does it for us.
She knows the tool pretty extensively, but we don't rely on external consultants to do it. We have somebody from our company who does it for us and acts as our own Jira professional. They would be the one that basically helps you with the setup for your project needs.
I don't handle the finance side of our relationship with Jira.
As far as I know, no other solutions have been considered as we've been pretty satisfied with this tool.
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.
I use this solution for general issue management, software planning, and change management.
This solution is a one-stop-shop for issues and plans.
Issue linking has enabled teams to trace issues.
I like the dashboards and Kanban boards.
The development links to GitHub are critical.
The only thing that JIRA doesn't for us is release management in a way that I can create a list of versions easily.
The primary use is task management. It has performed okay. It is easy to configure and maintain. It's quite simple to track tasks, then link with other applications/solutions from Atlassian, like source codes.
I would rather have a tool that we do everything on. Also, we have access to end user policies where we can configure them and give access to the correct person. We have tracking of who works on what and why over the history of a project.
Workflows, because we cannot employ a different approach depending on the speed of the project or customer. Whether it's research, engineering, or maintaining the process, we can cope with processes easily without adapting the tool, but adapting the tool to processes.
There are no fields to search or to filter by, mainly the ones which use a data around a date and time when something changes. So, you have to use some add-ons and create a lot effort to obtain information from the tool. Thus, you have to adapt to the lack of search that the tool does not offer.
So far, so good.
I don't see any problem with it.
In the past, I had training from the distributors and it was okay.
The tool is very easy to use. What is important is that we don't have to wait so much for contracts or more hours to have support. This is something that we have, and it is good for this solution.
Everywhere that I worked, we started by using spreadsheets, then we moved to some free tool, and finally to JIRA.
As far as I know, the initial setup was very simple and straightforward.
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:
I use the solution in my company as an ITSM tool. Our company's service desk and those working with the engineering team use the tool.
The integration between Confluence and Jira, along with Jira's ticketing system, is a valuable feature the product offers its users.
I opted for Jira since it was offering ITIL V4, and there seems to be a compatibility between ITIL V3 and ITIL V4.
From an improvement perspective, it would be better if Jira could offer more in the area of data analytics similar to what Power BI and Qlik offer to users. The tool currently lacks in the area of data analytics.
Jira needs to consider lowering its prices considering the competition in the market.
I have noticed a problem with Jira in the Philippines. In the Philippines, there are only a few companies that offer local support, which is alarming. In my previous company, when we requested support, basic support was not provided, and we had to schedule and deal with everything on our own.
I have been using Jira for around two years. I am a user of the solution.
It is a stable solution.
It is a pretty much scalable solution.
The solution's technical support is good. I rate the support a nine out of ten.
Positive
I have experience with ManageEngine and ServiceNow. If I need to deal with a project involving retail business, then Jira would be a poor choice because dealing with a retail business requires a tool to have an approach different from what Jira offers. Compared to ServiceNow, Jira is a bit better.
The product's initial setup phase was straightforward.
The solution is deployed on the cloud.
The solution can be configured within a week or so. If there are changes to be made in the solution, then it requires more time to configure it.
If I compare Jira's licensing model with that of other products, I think that the other products have a much better licensing model. Considering what is happening in the market presently, and as people are moving away from Jira and ServiceNow, more and more people have started embracing cheaper products in the market. I rate the product's price a four on a scale of one to ten, where one is cheap, and ten is expensive.
It is important to know that my company uses the free version of the solution since we are not a big organization. My company is currently looking into the configurations and other areas before going for the paid version of the solution.
Performance-wise, Jira is a good solution, but the problem lies in the part of its licensing area.
I rate the product's price an eight out of ten.
We are using it for software development tracking, bug tracking, feature tracking, and so on.
We are using the cloud version from Atlassian, and we have its latest version.
The way we can define and customize the search queries for the tickets in Jira is most valuable.
The way to configure it can definitely be improved. It is very difficult and complex to configure. Its configuration should be simplified.
I don't have any requirements for new features. It is a standard system, and we use just a part of the functionality.
I have been using this solution for five to ten years. I use it on a daily basis.
Its stability is good. In the last five years, I haven't seen any outages.
We are a very small team, and we don't have any requirements for scalability.
I have not contacted their technical support.
The initial setup and the out-of-box features and functions are very straightforward. I would rate it a five out of five in terms of ease. You can just create an account and start to use it.
It is a cloud solution offered by Atlassian. There is no on-premises setup, and it doesn't require any maintenance from our side.
It is subscription-based, and we probably pay yearly. I would rate it a four out of five in terms of price.
I would rate Jira an eight out of ten.
We are using Jira for the internal project and issue management or tracking.
The most valuable feature of Jira is the integration with all the different Atlassian tools. They all integrate very easily.
Atlassian has multiple tools and it becomes difficult for a customer to process everything differently. Atlassian should combine them and form a single solution for DevOps by including the Jira Confluence, Bitbucket, Bamboo, and others. This would be much easier for customers by purchasing a package, rather than purchasing bits and pieces. With Azure DevOps and other companies, it becomes easier to go with one company having multiple areas that they can cater to, but in Atlassian, the problem is that you have to select different solutions to have a full package. For example, to have document management customers have to purchase Confluence and for Git repository management they have to purchase Bitbucket, et cetera. There is always another add-on that you need to attach to have a complete solution in Jira.
I have been using Jira for more than five years.
I have found Jira to be stable.
Jira is a scalable solution.
I did not have any issue with the use of technical support from Jira.
The initial setup was easy.
I would advise others that Jira is a good solution and I would recommend it.
I rate Jira a nine out of ten.
I am an Agile coach and consultant, and my clients use Jira to manage Agile teams, including tracking and gathering reports on performance at the team level as well as the team-of-teams level.
Since I work with different companies in my consulting work, there are different versions and implementations of Jira that I deal with. Most of the time I work with Jira on-premises, although I have worked a few times on the cloud edition.
In the near future, I most likely be using Jira Portfolio instead of the regular Jira because that will be my new responsibility.
I enjoy working with (and can recommend) Jira for a number of reasons. The best features are that it is friendly and provides good visibility. It's to the point and very effective.
When I start work with a company, one of the promises I give them is that they will get visibility, and very quickly at that. We are able to easily create boards and have the teams start work with story points. Then, we will make use of the Structure feature, which is another good feature that we get benefit from.
In terms of the general Jira software, one element that is missing is budget management. Perhaps such functionality exists in add-ons, however. Once, several years ago, I tried to use one such add-on (the name of which I can't recall) but I dropped it because it was not effective enough. If we had this feature, I think we could provide the whole picture to top management.
I have been using Jira for about five years.
It is stable.
It's not scalable enough, in my opinion. To explain, I have a specific level of understanding of Jira so I am able to make specific customization to support activities at scale, but I don't feel like Jira is easily scalable out of the box. It's not always natural to scale up Jira without customization.
The technical support that I receive is not necessarily talking with any Jira support team, but rather it involves using the community's help from the internet.
On one hand, this avenue of assistance is quite good because I can often find answers there, but sometimes it's not enough. In these cases, Jira will ask to open a ticket and to vote on it so it gets priority. But it's frustrating because we might still not get answers, or we don't find anyone able to handle our issue for months or for years.
Overall, and for most problems, I think I have enough documentation so I can figure out what to do and how to do it. When compared with other tools, I think that Jira's documentation is clear.
I don't deal with licensing in my current consultant position.
For application lifecycle management, I can definitely recommend Jira and I would rate it an eight out of ten.
The solution is primarily used in a scrum setting for creating all the features, topics, epics, stories, backlogs, and helps manage the scrum.
It's a very powerful product. It works well with Confluence. It interacts with it well.
There are very advanced features in Jira compared to, for example, ServiceNow.
You can record your unit testing, regression testing, UATs, et cetera. With a wider universe of applications, it's very flexible.
I'm not totally a business analyst, however, a business analyst, can really, really use it very deeply due to the fact that you can register the results and create your test cases, run them, and document the results. All the testing is very advanced in Jira and it's very nice.
While it's very powerful, it's very complex sometimes. You can do many fancy things and have connections between features. With so many options, it's easy to get lost and it's not as easy to be on top of all the features and changes. In that sense, ServiceNow is easier to keep up with. Its configuration is more complex than ServiceNow.
The interdependencies between objects sometimes are not easy to trace back and to have a clear view of. That's why starting with small configurations is very important; we don't create very complex structures between objects in Jira. That said, sometimes when updating a history that was linked to an epic we would not understand why the epic didn't change when we changed the history. The relation sometimes can become complex. This is not a problem of Jira per se, it's a problem of how you configure Jira.
I worked with the solution for a while, however, I stopped using it. My last project was about 12 months ago.
The solution is stable. I cannot recall any issue with bugs or glitches. Jira never went down. It was reliable.
It is a scalable product. It can be applied with much more deepness, especially for developers.
Normally if I had some questions and issues on how to do what on Jira, I'd look for local support. We didn't have any Jira consultants or anything like that.
We also use ServiceNow. We use both products in the same way.
The configuration process is pretty complex. It's a pretty advanced product. You'll want to understand how to use it and what you want it to do before jumping in.
I would advise potential new users to start with simple cases in terms of configuration and to build on top of that in order to add complexity by identifying the need and not working from scratch.
I'd rate the solution at an eight out of ten. You need to get used to using it. It's a solution that can et very complex.