I am a consultant, and we have some customers with projects who use Jira.
We have customers with different Jira installations because there are so many vendors. It is mostly used as a bug tracking system with tickets, issues and tags.
I am a consultant, and we have some customers with projects who use Jira.
We have customers with different Jira installations because there are so many vendors. It is mostly used as a bug tracking system with tickets, issues and tags.
The feature that I have found most valuable is that it is a quite powerful user tracking system. Also, we use it to print tasks for planning so you can also see what's happening in the system and follow the tickets.
In terms of what could be improved, there is not much I don't like. It is a little bit faster but with Firefox it can be slow, but that is also the case with many other tools as well. It has quite a lot of options and fields, so I'm not too familiar with them all. That makes it a bit trickier. It could be a little bit easier, it is not that simple or straightforward.
The tool itself is so powerful and the customer's expectation is very high because you have so many things you can do with it. That can make it a little non-user friendly.
I would want to see Jira include some improvements, like drag and drop and color, to make it more straightforward. If you compare it to Microsoft or Octane, they have good features that I would like to see in Jira as well.
Overall, Jira is a little bit old fashioned, it could be more user friendly.
They should make it simpler, to just be able to do some functions, whereas now it takes longer. There are too many clicks.
I have been using Jira for around 15 years or so, but not all the time.
The stability is fine. We have some issue now with our customers, it could be due to the network or other issues, I don't know if it is because of Jira itself. We have quite a complex environment and system for our customers. At the moment we have several tools and different systems. We have some issues with downtime but I am not sure why.
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.
Our primary use case for JIRA is for entering user stories into the login books.
The most valuable aspect of this solution is its ability to connect everything together.
It also has good stability.
I have to go through a lot of processes to consider it done. I have to log in then change the logins and make it interesting. There shouldn't be the need to go through this. The process should be improved.
It's not so good for testing.
I have been using JIRA for ten years.
It has good stability until now.
You can scale with it.
We have around 35 users.
I haven't needed their support.
I previously worked with TFS.
There are a lot of similarities between the two. Especially in terms of working in the same field, tracking issues, and tracking bugs.
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.
We are using Jira as our help desk solution, as well as for managing our software development efforts.
Jira has helped with respect to managing our software development, although it does not suit us well as a help desk.
The most valuable feature is managing software development.
The help desk and services management features are in need of improvement.
I have been using Jira for five years.
This is a stable product.
The scalability is fine. We have fifty people in the company who are using it.
I have not used the vendor's technical support.
The initial setup was done before I joined the company.
I am currently in the process of searching for better help desk management solutions.
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 use Jira primarily for Agile development and change management.
The most valuable feature is its flexibility. There is flexibility in the structure, lifecycle, and workflows that you want to work with.
The interface is user-friendly.
I would like to see more robust release management within the tool. We're not able to use it at this time because of compliance issues within our industry. At this point, I'm not confident that it can meet the requirements.
I have been using Jira for about two years.
This product has steadily improved since the time I started working with it.
I would rate this solution an eight out of ten.
The primary use case is for software development teams to manage their work.
The most valuable features of this solution are workflow and reporting.
The team construct could be simplified. We use Jira with Tempo Planner, and Portfolio for Jira, and at times it is not always clear. With Portfolio, it's the same as Jira but with Tempo, it clashes. It's not a seamless transaction.
We would like to see integration between Tempo and Jira. For example, if I create a team in Tempo, I would like to be able to use it and re-use it Jira as well.
In Tempo, if you create a team then you are able to link that to a project in Jira. I would like to have that same capability, where I can link to Portfolio for Jira. Specifically, if I create a team in Tempo then I want it available in Portfolio. When I am planning the work for my team, it would be easier to have that capability available.
I have been using Jira for approximately four years.
It's a stable solution and we have not had any issues.
Jira is scalable.
We have more than 13,000 users and we have not experienced any issues with the performance or scalability. We are able to scale pretty well.
I work with Jira on a daily basis, as well as offer support to users and guide them into making the best use of it.
We have a relationship with Atlassian. I have not personally had to contact technical support, but I do know that we have a technical account manager to whom we report any issues.
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 primarily use the solution for project management purposes.
The solution offers up great transparency that makes it possible for everyone inside the departmental organization to see what's happening.
The prompt board really helped us out on projects. The scrum boards and the representation of the product backlog that helped us a lot as well. It's great for project management.
In general, although we use JIRA, we never really learned how to use it properly. The learning curve of the solution is high. It has a lot of power, and yet we don't understand its capabilities.
There needs to be more training modules and more emphasis from the company on proper training and product overviews so that users really understand its capabilities and can actually use the solution effectively.
I've been using the solution for nine years.
I do recall that there were a few times when servers went down, however, I don't really remember that much about why it happened. Usually, it got fixed very quickly. Largely, the usability was good.
In our organization, we had about 200 people using it and we didn't really have any problem with scalability.
Technical support is good, however, we haven't really used them on many occasions. We never have really dug into the solution to understand it, and therefore we didn't really need the help of technical support to walk us through anything.
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.
The solution's most valuable aspect is its workflow sensibility.
The user and group management could be improved in a big way. There really are a lot of administrative areas that require a lot of screens which could be improved in many ways.
A lot of the user interface could be updated.
Technical support is lackluster. It could be improved.
They need to address a lot of the requests that people have had over the last 10 years. Instead, they rely on third-party tools to provide these features. They don't seem to understand what it is their clients really need and instead just assume a plug-in can be made for whatever the purpose is.
I've been using Jira for ten years. It's been a decade now since I first started working on the system.
The solution is extremely stable. There aren't bugs and glitches. It doesn't crash or freeze. It's quite reliable.
The solution is absolutely scalable. If an organization needs to scale up, they can do so easily.
Technical support is pretty bad. They rely on partner companies for support and don't really have any of their own internal teams that can help.
The initial setup is not straightforward. It's quite complex. However, you do tend to get used to the process after a while.
The solution is quite expensive. I'm not sure of the exact pricing, however, I know it's not cheap.
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.
We have a development team and we use Jira to manage our projects. We use several products by Atlassian whenever we create and work on a new project.
We have scrum masters who write new project stories, which are tracked by Jira.
The most valuable feature is project management.
The integration and management features need to be improved.
When you first start to use the interface, it is confusing.
We have been using Jira for about one year.
In my company, we have a lot of knowledge and experience with Atlassian products. We have not needed to contact technical support.
I have also used ALM Synchronizer and I find that it is better because it is easier to manage and it is a more agile tool.
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.
