Jira Reviews

My people use ASS. I can define spins, I can define roadmaps, I can define components, I can do releases, I can define all kinds of issue types, heartbeats, some of those things. I'm using it for both business and software. In software we have Scrum and Kanban onboard, whereas for business we have the service and then there are those other options. We have multiple use cases. I'm the director of the company. 

I like almost everything about Jira. It defines how we track time and the way we define permissions. We can create multiple boards for the same product backlogs. 

I think that for users the solution is very intuitive but for project administrators, the way the product is defined is not very intuitive. There are too many ways to do the same thing. The setup of Jira sometimes becomes very, very cumbersome and difficult. It's not very easy for people on the project admins to really understand how to set up the product because of these features. If they were better organized and the documentation improved so that people would actually be able to figure out how to use Jira, that would be helpful. There are not many videos and it can be very challenging for anybody not familiar with the product. There are 50 users on the project I'm working on. 

I've been using this solution on and off for the last eight years. 

The solution is stable.

The solution is scalable.

We haven't really used technical support. 

The initial setup takes a bit of time because it has so many features that you should be aware of, but of course it provides a lot of out of the box features that you can use right away. You can set up in 10 minutes or 10 days, it's very rich. I was able to do the deployment myself with some extra help. 

For up to 10 users, the solution is free but above that there are licensing costs.

I would rate this solution an eight out of 10.

Our primary use case for Jira is for requests for tracking the software development.

We use Jira for the process, especially for password tracking. We're the issue management team for development. We are quite new, so I was very interested in ITSM documentation provided by Jira. But, I needed time to readjust that to our organization as per the line of business.

Overall I think it's helpful, but I need some time to absorb all the knowledge.

People have different opinions about whether it has improved our organization. I think it is quite a valuable tool and platform to streamline tasks, make project plans, and manage the release events.

The most valuable features are that it is good for tracking the issues and it provides for the usage of Confluence. The documentation is another supporting part for development. I didn't go that deep, so that's what I see as the end user.

In general, it's very convenient for people that work in the software development business.

In terms of what could be improved, it is a bit harder for management or the business partners. I used to search the Atlassian Community online for some troubleshooting issues and I think there were some issues that seemed to not be a big problem for other similar applications, like Microsoft Teams, that were not considered by Jira.

So I hope those will be considered soon. I think for some, the help documentation has been hard to track, so that I had a bit of difficulty finding the solutions. I'm the end user. I'm not the problem solver.

I have been using Jira for less than a year.

It does have some bugs or glitches sometimes. Like with Confluence, it always has some glitches, like the last edits I made minutes ago. It happens sometimes.

I don't know about the scalability. I just use the very basic one. 

Only our IT people are using it. It's easier for IT people to understand it than anyone else.

We have our technical support from our vendor. They are very supportive.

No, we didn't use another solution previously. We used to manage those processes manually, like the spreadsheet. That's why we would like to switch to the Atlassian platform for some automations and for a mature platform to help us.

We had our vendor help to set up originally. Later, we made some customizations by other means. But because this is still at a very early age for us, it's a bit random on previous customizations. There were some blockages for people to understand from different perspectives. But I think so far the business people may not understand those procedures because it was originally designed for the coders and for the software development business.

We are using the Community license for Jira since we are a not-for-profit organization.

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.

We use Jira for the overall issue management in development projects. We use it to maintain a high level during each sprint, which is a requirement. We also use Jira for issue management during testing. We create a test plan and manage it all with Jira.

Jira is very user friendly, easy to install, and easy to access. The most valuable feature in Jira is release management. You can also manage a consolidated dashboard that can be accessed globally by all the team members. We can do all this with Jira while engaging in development. 

One of the key benefits is that it's a single repository for all your SDLC. Based on the user ID and password, anyone can access it, and they also have a single sign-on. It's not that very complicated to do issue management with Jira. We can also pull Jira data and generate quality metrics that can be used for the overall optimization of the test execution. 

Although it covers the overall requirements and measurements, it'll help if they had their own test execution feature. Because right now, we're using third-party tools to test executions.

If there are multiple projects, it could be a good thing if they had a reporting method where you have a portfolio view with predictions and so on. If there were a way to manage all the SLAs, that would be helpful too. 

Jira is stable and meets our requirements. You don't have to use it out of the box as you can customize it to your requirements.

Scalability isn't a problem because we have used it with over 200 users. You don't have to stick to any out of the box features as you can customize them.

Almost everything is covered in their documentation. As payment is required for support, we mostly follow the documentation.

We used Microsoft DSP before. We were looking during a licensing phase for something where the non-licensing cost wouldn't be more, and the system requirement would be minimum. That's what qualified Jira, and we went with the data.

The initial setup is very good. I wouldn't say that it's very complicated. They have customization options for things like issue management. You can customize it based on your terminology and project.

For a simple set up, it may take around four hours. If it's a 20 member project, it's quite easy to set up Jira. But if it's to be made available enterprise-wide, it takes longer. I had complex projects where it took anywhere from three to four days or a week to set up. You should also note that it may take new users a week to understand it properly.

We tried to do a total uniform deployment, but it's not always possible because every project has some customization. A single user can deploy Jira. I have deployed and managed 20 to 22 users in a Jira instance. Basically, the Jira administrator creates the template. But if the project requires customization to write queries and run tests, that will require some additional skill.  

As a company, we get a subsidized price, and it's lower than what's quoted on their website.

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.

It is mostly used for communication, managing requirements, managing defects, and managing stories. We don't communicate much through Outlook. The majority of the work-related issues are assigned to us, or we assign them to developers through this solution. I've been using this solution for managing requirements and defects. I have also been using it for logging user stories and general communication.

Best in ensuring 100% test coverage through forward and reverse traceability matrices capability that allows users to track User stories, SRS, Test Cases, Test Instances & Defects all using simple links. 

The most valuable feature is the feature of assigning. Whenever I have an issue, Jira doesn't stop at just letting me describe the issue. I can also assign the issue to a developer, and the developer gets notified about it. After he is able to work on it, he can update the status and revert back to me through the same platform. It really avoids a lot of communication over email and phone. This the feature that I really like about Jira. I always use Jira with my team.

Produce improvements suggestions:

User Interface/ User experience could be improved by expanding on visual capabilities of links such as  Stories, Requirements, Scenarios, Cases, & Defects.

User Dashboards could be improved by increasing ease of use of charts and other interactive options such as Boards.

I have been using this solution since 2011.

It has been stable. I haven't had any downtime or issues with stability. It has been working as expected.

In terms of integrating Jira with other apps, I've actually used Jira to connect to ADPART or other client defect tools. Sometimes, I had to use the connections, but it was not a problem. There is a standard procedure where I had to request for the details, and after I got the details, I needed support from the client to get it connected. There were no issues, and the process is quite standard. It is not fast, but it requires some time.

At my current company, only I am using this solution. We are a startup, and we have less than ten people working here. However, on my client's site, a lot of people are using it.

I've used their technical support only once or twice in my entire experience with this tool. Once, I was not able to log in, so I had to call them, and the other time, it was a problem with my virtual machine. It was not a problem with the tool. I was having problems getting in. I raised tickets, and then I had to call them. It was nice, but it took a little bit of time. Overall, the customer experience was all right.

Before this, I used an HP tool. I started with using Quality Center, and then I upgraded to ALM, and ever since, it has been Jira. Jira is open source, and some of my clients prefer open source, and they have been using it for a long time. Before Jira, ALM/Quality Center was my major go-to tool.

It was straightforward. I just got the details from the client, and I started using it.

Save by reducing errors and improving accuracy.

Start with requirement. If requirement requires tight security and confidentiality, it is highly recommended to employ expert assistance. Whereas if the requirement is agile in nature and is at very initial stages, it is best to start leveraging open source to some extent.

It was solely based on requirement and preference of business stakeholders.

Some areas of business require to run licensed and proprietary software applications whereas some can have the opportunity to leverage open or closed source software. 

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. 

I have been the product manager for several years. I use it day in and day out to manage my team. I manage two teams at the moment and they are pretty large teams. Each has a minimum of about 12 people. We use not just agile, we use a scale model framework. All the work is managed through two pieces of software we use. One is called Jira Align. For the portfolio level software, what Jira bought recently, the previous name for the software was AgileCraft. All of the portfolios and features come loaded in Jira Align. From there, they will be composed into stories in Jira. That process is done using programming preventative planning. We do it every three months.

All of the stories are tracked. We have a workflow defined and we have statuses defined. As the team works on the story, the story moves from one status to another and we close them when everything gets carried over to the production release.

The workflow is the most valuable aspect of the solution for us.

The user story map is excellent. The features can be composed into stories and they can be allocated to each of the sprints in a program increment. It allows you to see all that in the user story map, and you have various dashboards to see the stories in various views. You can see them as a backlog view, for example, or you can see as an actual sprint view.

There are excellent reports that come out of the data for every sprint so that you can do metrics on each. You can measure how the team is performing with respect to burn down charts, or with respect to how many story points were produced, or how many stories were moved out. For this, you can gauge the performance of the teams very effectively.

The solution needs performance improvements. We see that a lot of times it's clocking whenever there's any abuse.

When we switch from one view to the other, it takes some time before that view is presented. The performance for different dashboards, whenever they are loaded, it takes more time than you're comfortable with. Whenever you move from one dashboard view to another dashboard view, then it should come up quickly. Right now it takes a long time and sometimes it clocks. The overall product performance, whenever you switch a view is what they need to work on.

Whenever you edit a story, whatever you have changed takes a bit of time to save.

The integration between Jira and Jira Align needs to be better. There's a lot of differences between the two systems. I believe what happened was Jira bought this software from a different company called AgileCraft. And that integration is still in process, and, because of that, there's a lot of differences between the statuses. That sometimes creates a lot of confusion for senior management whenever they're reviewing performance across teams. Better integration between Jira and Jira Align is on the top of my "most desired upgrades" list.

The solution should improve performance when there are multiple users.

I've been using the solution for about seven years now.

Whenever you load different views, it takes time. That's the only major issue. I didn't see any major glitches due to the fact that Atlassian is really good at catching them. The stability of this product is really great. I've been using it for, as I said for six, seven years now. I'm never unhappy with it.

Our entire company, whenever there's a new division that goes into the agile mode of developing software, brings on Jira.

It's really scalable, however, at the same time, you need to really throw hardware at it to offer better response times when you add users. That goes without saying for most of the software.

We currently have 2,000 users on the solution. We plan to continue to increase usage in the future.

We have an internal tech support team for Jira. We contact them whenever we run into issues. We have a platform for IT tickets. We use that to call them. I haven't directly called Jira Atlassian at any point, so I can't speak about their direct technical support.

I have used other packages for agile project management.

I wasn't involved in the initial setup, however, we have a Jira administrator and they have a group, and that handles it. I implemented Jira for my teams. I added users to roles on the system. Roles such as developer, administrator, approval, managers, etc. That is all done by myself. In terms of that task, and setting up a project, it's fairly easy.

Implementation is a multi-year process. Right now, the whole company is on Jira. Whenever there's a new group, it gets added, and a new team is created. It's always a work in progress and it's not very time-consuming.

I would say the training of people on how to use Jira effectively takes some time. It's very intuitive, however, at the same time, a little training goes a long way in utilizing the software in a much better manner.

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.

We primarily use the solution for product development efforts and documentation. We use Confluence as well for documentation.

Most of my work is keeping track of what's been going on and identifying what is blocking future work. What I like about this solution is you can create a consolidated customized dashboard out of your files to identify what's been going on and identify who has how much data assigned to them. You can begin to understand where roadblocks are and how to streamline efforts effectively. It's been helpful. 

The challenge which I frequently see from Jira is the label. When you search for a label sometimes, it suddenly disappears. If there's a mismatch due to all-caps or lower case, you won't be able to find it. It won't even come up as a recommendation or suggestion. That's something that can be really frustrating, as people create labels in their own specific ways and then no one else can find anything. While it should be a standard thing across the company to have labels created in certain way, the system should be able to pull up suggestions of labels that are close. 

The product could be more intuitive. 

If something isn't getting resolved, we generally aren't getting any alerts to warn us to this fact. We don't get any visibility on if something's been open for a few months even if it should have been closed after a few days. We need some sort of system that shows us items that are lagging.

I've been using the solution for about six months to a year or so. It hasn't been too long. Our company has been using it since they started doing development work.

In my experience, most of the time it's very stable. Sometimes we have a few bugs here and there in Jira. However, it doesn't affect our work in a very big way. It doesn't crash or freeze. It's reliable.

I'm not sure about the whole company, however, on my team, we use it extensively. We have around 30 to 35 people using it on this team. Obviously, they are using it on other teams as well, however, I don't know the count of each team.

In terms of scalability, we are able to add new users as needed, and that has never been a problem for us.

I've never had to reach out to technical support. I don't know how responsive or knowledgeable they are.

I didn't previously use another solution, Jira is the first product I've used for this purpose.

I actually was not involved in the initial process of the setup, therefore, I can't comment on the process. I have no idea as to if it was difficult or straightforward.

I'm not aware of any regular maintenance that is needed on the product.

I don't deal with the financial aspect of the product. I cannot comment on if it is overly expensive or not as I don't handle billing or payments.

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.

Our primary use case is for our own network operations, and integrating via API with our customers network operations teams.

It created excellent data points and summary with up-to-minute information.

The informatics is the most valuable feature. It captures what we need.

The user interface could be better, but the stability is definitely there and the accuracy is good.

The GUI should have much better features like more graphical illustrations. There are some cases or benchmark data that we are trying to capture and customised into a graphical pie chart summary dashboard, but unfortunately JIRA is not able to do that.

We implemented JIRA six months ago.

The stability is good. We have around ten users as a start. 

Impressive

We have contacted technical support. Their response was prompt. 

The initial setup is not that difficult, but it's not that simple either. That is why it took us  about three to six months to get it up and finalized.

Via our in-house.

Right now the price is fair but once they move to the cloud, that model may not be attractive anymore.

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 use Jira product in the organization to automate the software development life cycle.

It's a very flexible product.

We can change the workflows as much as we need and we've done that already. 

The workflows are very easy to handle as far as scalability goes.

If there is a feature or a workflow feature, that is required and it's not available out of the box from Jira, from Atlassian, we have the marketplace buy from. There are a number of add-ons that we use. We have maybe 20 to 25 that fill in any gaps in the system itself.

The user interface is very detailed right now. It could be simplified if they consider targeting the user experience. Right now, on the screen pre-design, the amount of information on the screen is very high. The distribution is good, however, the presentation itself looks very technical. They should work to streamline the UI to make it better for users to digest the information.

I've been dealing with the solution for two years now.

The solution is very stable. We haven't had issues with bugs or glitches. It doesn't crash or freeze on us. It's quite good.

The solution is scalable in terms of the number of users and the number of features. The features we are using are mostly out of the box, however, we have added product management features and code delivered with the integration features. We also have added test management tools or add-ons to it including reporting and dashboarding as well. You can really grow it out and add as many plug-in apps and features as you want.

Currently, we have 500 users that interact with Jira within our organization.

We have good internal technical support for Jira in the organization and we use the Atlassian technical support only when needed. Thus far, we are quite satisfied with the level of support we receive.

I cannot give too much information about the installation, as we're similar to a consultant, and I don't want to get into too many details. As the installation engine, we took two days straight to deploy it and that is with the implementation.

For deployment, you don't need a huge team. We did it with two technical personnel. They are consultant level system administrators.

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.