Some of the use cases are for tracking issues and bugs.
I am responsible for an administering job for Atlassian Jira at my company. I'm working for some of the major IT companies in Kazakhstan.
The solution is deployed on-premises.
Some of the use cases are for tracking issues and bugs.
I am responsible for an administering job for Atlassian Jira at my company. I'm working for some of the major IT companies in Kazakhstan.
The solution is deployed on-premises.
The solution is valuable because it's pretty flexible. It allows you to do a lot of stuff, and the functionality is pretty rich. It integrates well with other products, like GitLab, that we are currently intensely using at the company.
The solution could be more user-friendly.
I have been working with Jira within the past year.
The solution is pretty stable.
The solution is scalable. There are a few dozen users using this solution. We might increase the usage in the future.
I previously worked with ClickUp and would suggest using it. It's a competitor to Atlassian Jira.
When it comes to functionality and usability, I think ClickUp is better, but compared to Jira, ClickUp's drawback is their integrations with other products. The product is not old enough to be mature.
Jira is more flexible and more integrative with other products, and ClickUp is more user-friendly. The functionality is pretty rich.
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.
We use Jira as a help desk, an IDSM. We use it on a daily basis. Every ticket gets opened on it.
It's very simple to change the workflow and adapt it. Jira is very user friendly for the agent and the user.
It's a very customizable solution, but as a customer, we're always looking for additional customization. There could be better customization in future releases. If we changed from Atlassian to another product, we would look for a customizable solution.
I have been using this solution for many years.
The stability of Jira is good. We haven't had any issues with stability or performance.
It's a license-based software, so if you pay more for the license, the solution becomes more scalable.
Customer support is usually good. I have had no issues with them.
Setup was straightforward. There is no dedicated team for maintenance. Our IT department handles that. It's a simple solution.
There are no additional costs to the standard licensing.
I would rate this solution 10 out of 10. I recommend Jira. For the time being, everything is good. Their support is good. The platform is good. There are no issues with them on any level. We mainly picked Jira because of its stability, integration, and price. If a solution is well integrated in our environment, and it's not costly, why not configure it?
The biggest thing I have taken away from working with Jira is that it's very simple.
Our company is a consulting company and then we are an Atlassian partner as well. Therefore we use many functions of Jira. It's sometimes project management and sometimes to communicate to outside customers.
The solution is very fast.
It's a very useful tool. Jira is very useful for project management for internal projects.
We can easily communicate with many things easily in Jira.
There's the ability to easily customize the product. There's lots of great potential functionality.
The solution is stable.
You can scale the product very well.
We'd like to see more collaboration tools implemented within the product itself.
The product needs to allow for more communication between individuals and teams.
The solution could always use better reporting.
I've been using the solution for four or five years.
The solution is very stable. There are no bugs or glitches. it doesn't crash or freeze.
This is the type of tool that would work well for any size of organization, from a smaller company to a very large enterprise.
The product is very easy to scale and extend the user license. In terms of functional expansion, for projects, it's very easy to expand. You can do so in no time. It's very quick.
For the most part, we are satisfied with technical support. Sometimes in some areas, if you find a bug on Atlassian, they respond quickly. However, sometimes, they are slower. It can really vary. For the most part, they really try to get to things quickly.
The initial setup is different and is case by case, however, for a single person or scrum team, it's not too hard. The process is simpler on smaller setups. The more processes the company needs, the more complicated the solution gets during implementation.
We have our own engineer team internally that handles maintenance. We have no problem with maintenance tasks. It's not too hard to handle.
We provide implementation services to our customers.
Jira pricing is very difficult to pin down. They stopped another licensing version earlier in the year, in February. Now they have only data center licenses and then cloud licenses. These are more expensive than a server license. With a server license, you pay once. When you get a cloud license, it's an ongoing annual cost. We would have preferred if the old licensing model was kept.
We are Atlassian partners.
We are using the current version, the latest version right now.
We use both cloud or on-premises deployment models. It's a hybrid approach.
I'd rate the solution at a nine out of ten. I'd recommend the product to other users.
We primarily use the solution for our own projects.
The solution, for the most part, offers good usability.
The ordinary user has an interface that is very clear.
It's very easy to collaborate, especially on-site when there are a lot of moving pieces. It's a great collaboration tool.
Some of the interfaces, especially on the administrator side and for permissions, are not so clear. They aren't very user-friendly.
For admin to get permissions and stuff like that for their members it's a little confusing sometimes. That said, the rest is very clear.
The integration of what we call "Issues" in Jira could be better. The Issues integration with Bitbucket Pipelines could be better. If Jira can provide an easier way to configure and use this functionality, that will be helpful for workers.
I've been using Jira for more than ten years now. It's been a while at this point.
I looked at other options, however, Jira is so famous and well known that I did not have to look for other software.
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.
We use this solution to manage our projects.
Jira is a great software. There is not much to complain about, other than it doesn't fit very well into our current Microsoft environment.
Jira as a structure has Confluence for documentation, and for what it is offering it is a strong suit with Atlassian.
The only thing in our current setup that is a bit difficult is that Jira is a bit of a black box. Only we see it, our customers do not. I know that we can change it but we have not done the work to do it.
Jira is not compatible with our current Microsoft infrastructure.
We are using SharePoint along with WorkPoint in our environment, which is used for document management and process management. For projects, it is a better connection between HelpDesk and the projects. Moving into SharePoint would help.
If Jira would be interested in offering a SharePoint version, it would be beneficial.
I have been working with Jira for approximately five years.
Jira is a stable product.
We have approximately 50 users in our company who use Jira.
I am satisfied with the technical support of Jira. It's fine.
I have tested Plumsail Helpdesk. There's only one thing that worries me. Due to GDPR, we cannot use email yet in Plumsail. That is the only thing, use email to create tickets.
I don't know where the mailbox is in Plumsail, otherwise, it just ends up in us using SharePoint. It looks very promising.
It is very affordable at the entry-level. When you get larger, the pricing becomes very, very steep. It is the same for many other solutions, but I find it expensive when you get larger.
We are currently using Jira but want to move the help desk to SharePoint.
We have a Microsoft environment. SharePoint HelpDesk would fit better into our environment. As we are larger than we originally started, we have to make some changes to our current setup.
I also find Plumsail HelpDesk quite interesting.
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.
We use Jira to manage our software development lifecycle. Additionally, it can be used to communicate between teams and as a management tool, it has many abilities.
The solution is easy to use and user-friendly.
I have been using Jira for approximately 10 years.
Jira is highly stable.
The solution is scalable.
We have approximately 400 people using the solution in my organization.
The technical support is very good. They have different ways to get in contact with the support, such as chat.
The installation took a couple of weeks. It was a distributed architecture that was quite easy to implement.
We are on an annual license and could be less expensive.
I would recommend this solution to others.
I rate Jira a ten out of ten.
We use Jira for our in-house projects. We use Jira Cloud and Bitbucket. We are not actively using Confluence.
We are a small company. We can manage our project tasks with other tools, but I prefer to use Jira on the cloud because people forget what they have done, and we need to see who did which task and when.
We love the bulk edit feature. Jira also integrates well with Bitbucket.
Workflows can be improved. We don't use workflows because we can't handle that much complexity. Its interface could be more intuitive for workflows.
I have been using this solution for three years.
It is very stable. I have been using this solution for three years, and I never had to contact their support.
It is scalable. We have six people who use Jira at the moment, and they don't have any issues related to slow response. Everything is fine for now.
I never had to contact their support.
In this company, I have only used Jira. In earlier companies, I have used other tools such as Microsoft Project, Redmine, and Service Bus.
It is easy to set up. We can use project templates. We can use classic projects templates or create new templates. Classic is enough for us. Our management doesn't want reports from us. We use templates for our daily progress.
Its price is good and similar to other products. It is about five or six dollars per user.
I got it set up when I joined this company, and now I manage users here. It has integration with Bitbucket. It is fine for us.
I would rate Jira a nine out of 10.
I'm a consulting company. I provide solutions for many companies, and in some cases, I implement Jira. DevOps is something else that I provide for my clients.
Our clients range in all sizes. I have microscopic clients, such as a one-man company, and on the other end of the spectrum, I have the New Zealand government, for example.
The most valuable feature of Jira is that it's a well-known tool that many people are familiar with.
Jira is not the best tool; I just don't like it.
I am not looking to improve Jira. I have transitioned to using Azure DevOps or GitHub.
I don't like the interface or the way it is structured. I prefer the way it is done in Azure DevOps.
It is not user-friendly.
I have been acquainted with Jira for approximately five years.
Jira is a stable solution.
I have not contacted technical support.
We are also providing Azure DevOps.
I would recommend DevOps because it is more user-friendly and easier to use.
I was not involved in the initial setup of Jira.
I would rate Jira a five out of ten.