Jira Reviews

Right now, I'm just trying the solution out. I'm doing a POC.

The solution helps a lot with scrums.

It's great for development. 

The documentation is quite good.

It has some automated software testing which is useful.

I'd like some more features around software testing. I'd like to see some more stuff done around data testing. That's what I'm most interested in.

They could be better around generating documentation and essentially helping with test scenarios, test cases, or test results in a way that is more user-friendly.

The product needs to be more flexible to adapt more effectively. Sometimes you fix the style or the format and it might not suit the environment. I'd like to be able to more effectively configure it.

I've only used the solution for less than a year at this point. It hasn't been too long.

The solution is quite stable. It's not really buggy and it doesn't crash or freeze. It's pretty reliable.

The product can scale if a company needs it to. They should be able to expand it to have it meet their needs.

I haven't really dealt with technical support. I study the solution mostly on my own. I've never spoken to them and therefore can't speak to how their services are.

In a few months, once I have used it on a deeper level, I may get the chance to reach out. However, as of right now, that has not been the case.

The initial setup is not complex at all. It's quite straightforward. We didn't have any issues with it.

I'm not sure how long the deployment takes. I'm a lecturer and consultant, and therefore my role is more to help people use the tool rather than set up the tool for them.

I use the free version of the solution. We don't pay for it at all. 

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.

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 use it for project management and agile scrum projects. I am a manager, and I work with backlog tools and sprint plans. I only use Jira for backlogs, sprint reviews, and data reports. Our project manager is the person who is really working with Jira along with the team. We also have Confluence and Bitbucket. We use CloudBees and DevOps for the deployment of the environment.

It is easy to deploy in the cloud and other environments. It is also easy to view the reports of the sprint review or the sprint plan and the relation between the backlog and the repositories.

I am not sure if Jira can be integrated with our ERP. We have our ERP for the cost estimates or measurements. It would be nice if we can check or view a plan with the real cost. Currently, we have to do a double check of costs. It would be better to be able to integrate it with Jira.

I have been using Jira for almost one year.

I don't work too much with Jira. I use it only to see the reports, and I don't feel that there are many bugs. It is stable.

It is not too expensive. It is just comparative to other tools like Microsoft Teams.

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.

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.

Virtually every day we have our daily scrum. Our team gathers around the board, which has all the columns showing where the tasks are standing: requested, planning, ready-coding, review, etc. Together, we view one task after the other and update the statuses. It's really a focal point of the team to know where the work stands, and what's the progress of the work since the last time we checked.

Within my company, there are roughly 25 employees using this solution. We have a scrum master, who's the most knowledgeable person on the tool. usually, they're the ones organizing the tasks, creating new tasks, and then creating the report at the end of the sprint or the quarter. They're the person who's creating the reports, using the more advanced features. That's the scrum master.

There are the developers, including me as a tech lead. There's the tester. There are managers — once in a while we have to present them with some reports and statistics, so they know how much work is being achieved, but they don't have in-depth knowledge of the tool. It's really an internal tool, so the customer is not involved.

We're not expanding much at the moment. We've been expanding in the past year, but now things have slowed down a little bit due to COVID-19.

With the help of Jira, tasks are less likely to remain stagnant for a long time. We always see them somewhere on the board. Nothing gets forgotten — it forces the team to make a decision on every little task that is planned.

The way we can quickly see in which state a task stands — with everything classified by columns. It's easy to know who is taking care of what. For instance, if I want to know how busy the person in charge of QA is, I can easily see what staff members are working for him via a little face icon or a tower. I can see who is responsible for what tasks. The board gives you a quick summary of the workload of everybody on the team.

When a task is completed, it disappears and I don't know how to find it. If I want to go back in history to review an old task that we completed, I cannot find it. Unless you remember a keyword or a task number, it can be very difficult to find old tasks.

Sometimes, in the display, there is an overload of information that makes it very difficult to read. If there's too much information, it defeats the purpose. You have to reach a balance, and I think at the moment, there can be too much information.

Sometimes the interface is too crowded. It seems like the default option when you open a task is that everything is open and all of the menus are deployed.

There needs to be easier integration with third-parties — personally, this is the biggest issue for me.

I have been using Jira extensively for one year.

Atlassian tools from the Atlassian suite are all linked together. We use GitLab. We wanted to integrate GitLab with Jira because whenever we create a branch in GitLab, for a repository, we create a branch to develop a feature or to fix a bug. Once the work is done, we have to merge that back into the master branch. When we do the merge, we name the merge and we enter a reference to a Jira issue.

It's easy after that. The person who's taking care of and viewing the merge requests can just click somewhere on a piece of information in the merge request, and it brings you to Jira, to the associated tasks. Usually, for each task, we end up creating a branch; it gets reviewed and merged back into the master. Once the review is done, it's ready to be tested.

That's our work procedure. Basically, the two tools — GitLab and Jira — need to be integrated with each other, but at the moment, there is a bug and It doesn't work. IT reported that problem to Jira or GitLab, but we have not heard back. 

There is a problem when it comes to integrating Jira with other tools, or other tools with Jira, there seems to be a weakness there.

Adding more users is not a problem. We haven't tried to add a third-party or to integrate with a third-party, so I can't comment on that. 

We don't tend to use Jira outside of its purpose at the moment. It's hard to answer this because we just add or remove users; we're not trying to upscale it to a higher scope or anything.

I go through IT for technical support. Except for that problem I mentioned, the integration between GitLab and Jira, we tend to find the answers pretty quickly.

Jira offers good technical support.

I didn't help with the initial set up myself. Since we have web access, you don't have to install anything. It was already installed when I joined the company.

Our IT team handles all maintenance-related issues. They don't necessarily know all the menus of Jira, all its capabilities, but they know how to deploy it.

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.

The timeline management is great and the dashboard allows me to see the performance of everyone working for the company.

The filtration could be better.

I have been using Jira for six months.

Stability-wise, it's not the best, but it's stable.

Jira is very easy to expand upon and customize.

The initial setup was very easy. It's a very user-friendly solution but sadly, deployment for Jira is not the best.

I would highly recommend Jira to other interested companies.

On a scale from one to ten, I would give Jira a rating of eight.