Jira Reviews

There are so many use cases for Jira. If it's got something to do with IT, it will be covered by Jira. They have a very extensive marketplace and you can find nearly every solution there, including version controlling, source control for the code, automation, test automation, security scanning, configuration, and development management. 

What I find valuable about Jira is that it's an ecosystem. Sometimes, it does not provide the best-in-class solutions, but it's so well integrated. You will not have many problems with integration.

The transfer of the functionality between testing or pre-production and the production environment could be improved. It would be helpful to have more automation in this area.

I have been using this product for three years. 

In general, the core of the product is very stable.

Approximately 150 users use this product at our company. One comment I would have regarding scalability is that I noticed Jira is not yet ready for the Docker platform. I think they are working on this and it will improve the scalability of the product. 

Overall, their support is okay. Many topics are covered in their documentation or on Atlassian. We receive support from a local partner.

We previously used SISA. 

The initial installation was straightforward for us. What could be improved is the migration between the testing and production environments. This could be automated somehow as the manual transfer of certain workflows and functionalities is very time consuming right now.

On-premises

We use this solution for project management.

It can be used across a team. Managers can assign tasks and then they can track the progress. They can put the start dates, end dates, and everyday comments.

They can upload the relevant files to that module.

Jira is used to manage a sprint, which is the terminology used in the agile practice of project management. Sprints can be tracked fully using the Jira software. A sprint is typically a part or a subset of the entire work. It has a definite goal.

For example, if I am building test software, and building the login page is one module, then I can track the work created from the starting stage to the end.

It's a part of an entire software application. If a login page of a website is a subset of an entire website, I can track that right from when it started, how long it takes, what is pending, and how long the control test is.

Basically, you can clump it all together as if it is a team and you can measure the speed of the team. It enables the predictability of a project and helps determine when it can go live.

All of the tracking features are the most valuable because it allows me to see where we stand today and every day. 

At the end of the day, I look to see what is pending, what is as per my expectation or as per the speed, and what is not going.

I can put in my comments or give a direction, or tag any other person if they need any help if they are stuck.

The user interface could be much better, although it's good enough to do the job.

I don't see the mobile application for this particular application. I use it on PC. I tried to download the application, but there are some constraints to using it. It doesn't link properly, it doesn't detect my Jira board, even when I have entered the name. I don't know how to use that app. I download and tried, but there is confusion. There is no clarity on how I can map my desktop account with the mobile application. There is definitely room there to improve. 

There should be a way to integrate the mobile application or in some way, make it more clear because at first instance, I didn't understand how to use it.

We have used Jira over the last seven months.

It's a stable solution.

We have a team of eight members who are using Jira. They are divided into teams with each team using different boards. 

For example, one team is managers who are using it, whereas another is a team of developers using a different board that can be created and used for their purposes.

I have not been in a situation where I have needed technical support. Everything has gone well.

The installation is typically done by my IT team. I don't have exposure to that.

Prior to Jira, we were evaluating Microsoft tools, but I don't recall the name. Possibly Microsoft Task.

We were evaluating Microsoft products for the same purpose.

The decision is a collective team decision. It may have been that Jira is easier to implement across the company.

It is a well-crafted product. I don't have any concerns.

I would rate Jira an eight out of ten.

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.

On-premises

We use it for capacity planning. We need to gauge and assess whatever is coming to our pipeline and then everything comes to the pipeline, appears as a pic, and then based on that, we create the story points and we take it from there. With that, I am able to create a kind of gauge, estimate, and forecast our capacity planning for the next two weeks. We use it to create peer reports.

A more organized hierarchy is important. Reporting and JQL create issues for me. They do not completely cover the reporting part that I need to report in terms of my capacity to plan. In the same token, there is no record at this very moment to provide me with one export with epics story points, tasks, or issues and their sub-tasks at the same time. So I have to do multiple exports to just create the sub-tasks and sub-tasks are not being reported. If I wanted to export this and recreate this in another platform like Azure DevOps, I would have a problem right now.

I have been using Jira for four months. 

The support person I contacted was not skilled enough to provide me the answer so it's up in the air.I'm just doing multiple exports. 

Jira as it is, is a very nice tool. For capacity planning and resourcing, I think it is not built for this and we are trying to make use of it in that area.

I would rate Jira a seven out of ten.

Public Cloud

Team level agile project management.

Agile teams work with this tool. However, scaled agile support of this tool is limited.

• Dashboard possibility
• JQL query
• Workflow management.

Tree view of linked issues.

More than five years.

We are working in the safe channel process in the IT part of the bank. It is a good experience overall, but the look and feel for the user is not good.

It benefits us because we have globally located teams. Our team members work in different geographies, so the product is a better way to manage progress and see the status of different tasks. Otherwise, it is not possible to work in different geographies.

I can drag and drop to the different statuses. I can go into the task and change it, then I can directly drag and drop it from one status to another.

There is a difficulty viewing all the attachments because they are shown in one place. I would like attachments to be shown at the comment level. Right now, if I attach something, it will go into a single attachment pool for the task, not at the comment level. I.e., If I want to attach the new version of a document, it creates confusion because I have to remove the existing attachment.

When writing comments, there are not many options for formatting. We were expecting formatting something at the level of Microsoft Outlook or Microsoft Document.

When creating a task, there is no place to add our estimation.

Three to five years.

Sometimes, it is slow and hangs. We faced some stability issues where JIRA was down for a day. Also, we have lost some of our comments made in the JIRA because of downtime.

I don't have any issues with scalability.

We haven't used it.

We did not have a previous solution.

I would tell a colleague looking for this type of solution to look at Microsoft TFS and VSTS. 

Most important criteria when selecting vendor:

• A well-known vendor for the software.
• A good reputation.
• Compare what other companies are using.
• The look and feel of the user interface.

Managing our entire product development life cycle, as well as all test cases and test runs. That include at least 4 developers, 2 business analysts and 2 testers, all working on sprints. 

Before JIRA we had to create our PRDs, our product definitions requirements in another feature, then using another tool to organize the combine with all the JIRA tasks.

Now with JIRA Tasks, our product technicians can use the JIRA module to manage tasks by creating PRDs and user stories in JIRA, or even in Confluence (another product from Atlassian). Then, our PBAs, our business analysts, use Confluence to create all the definitions, which we can then use to create user stories in JIRA using the combine module.

The most important is the Agile management, because we use Agile in our everyday tasks. Also, the task manager is important.

Right now, the Task Management feature and Confluence are separate from JIRA itself. So, we have this problem where sometimes these modules don't talk to each other the way we expect them. So many times, links created automatically from new tools apart from another tool which didn't work, therefore you have to manually go into the task, even though the link is right there.

Another example, in JIRA you create a test sessions with user stories, then buttons from the user stories can automatically change the status of a test session from started, completed, or paused, which doesn't work. Therefore, there is a problem there: inter-module conversations.

Three to five years.

It's pretty stable. It doesn't go offline very often.

It works great for scalability. We have many users with more users coming. Our current users are on the road and can work.

Right now, we have a technician, a specialist, in another country that works closely for JIRA. So, we don't have technical support directly with them.

I used just Excel sheets. JIRA was a major improvement for a variety of reasons listed in other answers.

Even though, JIRA was a new thing at the company that I worked for, it was pretty easy to setup. The product is fast, so you don't have any frustration with installation. Account creation was pretty easy, too. Not too complicated.

We tried Microsoft, but it only supports task management. It doesn't support creating test sessions the way we like to them. Also, it doesn't support product definition the way JIRA supports us and Microsoft's general interface is a whole mess, so we prefer JIRA.

Learn every module you use (a lot!) before jumping to other modules, like we did, with JIRA Testing and Atlassian Confluence, because the conversation between those modules can be troublesome if you don't know exactly what it wants.

The product helps us a lot. It can handle the main features that it's supposed to in a proper manner, so we don't have any frustrations in our daily activities.

<ul> <li>Customizable workflows</li> <li>Agile / Scrum compatibility and offerings</li> <li>Granular access/security settings</li> <li>Large selection of add-ons</li> <li>Ease of use </li> </ul>

Since our service is customized to each client, the ability to customize workflow for each project's specific needs has improved productivity simply by streamlining our efforts.

We switched to JIRA this past February. So 7 months.

There is a steep learning curve for administration. While the tool is fairly easy for our users to understand and use, what it takes to set up the system to MAKE it easy for end users is fairly complex. There is a large amount of information to know and many interdependent layers.

We did not encounter any stability problems due to the JIRA itself. The problems we ran into were server-based and improved significantly after upgrading our server.

Not yet. =)

Customer Service: I would give it high marks. From an account service standpoint, all of my questions and requests have been replied to quickly and thoroughly.Technical Support: Medium-high. It mostly takes the form of Q&A within their Atlassian Answers forum that then leads to links of posted documentation on their Confluence pages. So there is a wealth of information and people able to offer advice and help. But it has a very "self-help" feel when trying to track down answers.

We did previously use a competing solution. We decided to switch based on several factors: cost, (lack of) support from the previous tool, and mostly we felt the strengths and weaknesses of the prior tool did not match up well with our needs and processes.

It was complex, but in a good way. We used a vendor called Service Rocket to help us through the process and they were magnificent. We spent several weeks with them as they got to know our process and needs to help tailor the setup solution. So it was complex in that we spent a lot of time closely examining our processes and workflows to make sure the solution fit accurately.

We looked at numerous other products. Some were more well-traveled offerings like Rally, AtTask, Clarizen, and Basecamp. Others were newer to the game like 10,000ft.

The most frustrating part of implementing a new management system is "you don't know what you don't know", so it's easy to miss which questions to ask or requests to make. JIRA has a LOT of knobs and levers to pull and is many layers deep in it's setup. If you're not intimately familiar with its offerings, I highly suggest using a consultant or vendor to help step through the implementation. I also suggest being specific in needs and wants. We’ve found JIRA is flexible enough to adapt to our needs more often than we have to adapt to its offerings.