Jira Reviews

It's really for Agile projects with storyboards, and then defect management.

The performance has been okay.

It has improved the Agile process in our company.

A lot of people in the business work with this tool so when you are searching for a new employee you don't need to train them on this tool. 

The reporting and the view, from a story to a defect, should be improved in the next releases. For example, how many boxes are assigned to one story, or how many tests are run on one story, and so on. This is what I miss in the tool at the moment.

The stability is very good.

We are about 700 - 800, and it works. Not all use JIRA but in IT we are 100 people.

I have not personally been in touch with support, but I think the support is very good. I haven't heard anything wrong with it.

We have two organizations. One is development, and they work JIRA. And the other is the business, which is responsible for testing. At the moment, we are going in the direction of DevOps and more Agile, and we would like to merge our tools together.

The important criteria when selecting a vendor, in my opinion, are that the vendor should be flexible, cheap, and the support should be excellent.

I rate it an eight out of 10. It's easy to use. People can become productive with this tool in a short time, and it is really the right solution for an Agile environment.

A lot of solutions show very well on paper. When you are selecting a solution, do a proof of concept in the environment.

We run pilots and product development using this for Agile and Scrum applications, in mechatronic product development.

It has performed well so far. We like it, we would like to expand it.

It's a tool that won't change the way that you work, but it supports the way that you work. Agile is changing your teams, changing your organization, the way that you work, and then JIRA will help you doing that across multiple locations, for instance. 

We don't do physical boards. I run a team with four locations, in three time zones. I need to work with online tools, and this is where the tool helps me. It helps me to use virtual Scrum boards across four locations, three time zones, and to plan my work.

The most valuable features are 

• the easy handling
• drag and drop
• what you see is what you get.

It's, smooth, accessible. It fully supports the Scrum approach, and the Agile way of working, and it has Agile thinking behind it, so this is very much helpful.

I struggle with Epics, how they are implemented in JIRA, because they don't work like any other Story, in a good way. I see a list of Epics, but although I can order them, there are some mismatches with how the Epics are used compared to what Scrum expects, or what Story mapping expects an Epic to be. 

For instance, if I rate an Epic, the Story points, and I rate the related user Stories, the Story points, they all count together. They're all summed up together. So, the overall Story points for the Epic, including the Stories, is double of the Story points. It just doesn't make sense. Maybe I'm doing something wrong, but I had to delete all my Story points on the Epics because they were counted including the Story points. This is not correct, and I would immediately improve that. 

I would like to see visualization of release planning. I can list the releases and I can give dates to releases, but to show how they are happening on a timeline, I would need to order the Portfolio part. But just for this, it may be too much to use the Portfolio for that.

The stability of the solution has been near perfect. I haven't faced yet any technical interruptions. 

There was one issue we had, technically, when we added 30 more users. The server hung. I don't know whether it was because of the tool, or what the reason was.

Scalability, I can't really touch yet. We have small scale approaches. We are about to scale. I think the idea about how to scale is not yet clear. It works perfectly for a team, that is pretty clear. How you do this for more teams, I haven't investigated this too much. Maybe the tool contains this, but currently it's not fully clear to me.

We switched because the visualization is a great help. So, really to transfer from a physical Scrum board to a virtual Scrum board implemented in JIRA, as well as so teams can work with us, and collaborate with us, on a Story to produce a result. Recently we tried to work with PDC task management. As a team, we had to learn it. It's possible as well, but not as easy and flexible as JIRA.

I'm not the selector of the vendor, but from what I can tell, from what our IT selects, the vendor should be 

• available for global support, should be accessible in 24 hours, if there's a larger issue
• able to collaborate with large enterprises, which sometimes have different cultures, different languages
• able to integrate into the existing work environment - we have this tool, and that tool; the tool should fit into our tool landscape
• able to provide training.

I would rate JIRA a nine out of 10. It's not a 10 because it's inconsistent, sometimes, in how it acts and reacts, like my example with the Epics. But it's a high rating because it's user friendly, it's easy to use, you do not need much training on it. If you know how to work with Scrum, you can easily use it for your own work in a small team. For multiple teams, I'm not sure. I can't judge this because I haven't done this yet.

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.

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.

JIRA is an issue tracking application, it in global development projects. JIRA helps teams to track and accomplish the items that need to be The great feature about JIRA is you can store the activity happening around an asset in one placeJIRA is useful in project management. It can reduce the rework in enterprise projects. You can also use JIRA Core for Project management, Task management, Process management, HR, Marketing, Legal and Finance projects. JIRA Core can be as per business projects need.

JIRA is very efficient. It helps us to create benchmark times to solve each ticket's severity. Burn down charts show your effort against the estimated time.

Active sprints. It is like a Kanban Board drag and drop backlog to assign, to do, and finish the task.

When creating Epic, Story, and Task, there is no provision to set estimated time. The estimated time can only be set once the ticket is created.

No.

No.

Excellent.

We have In-house project management tool. The report generation, burn chart are not so good. We Started to use Jira to  between different projects across geographic location

Straightforward.

In House

Its very nominal  prices per the features available.

No

JIRA is very good. With another tool, like Confluence, HipChat, Trello, Bitbucket, Bamboo, and FishEye. It creates a robust project and product management process.

We used JIRA for:

• Writing down requirements and stories.
• Analysis
• Creating tasks, subtasks, and defects.

It also helped tracking the sprint process more efficiently.

It gave us control over all test artifacts in one place, along with easy traceability, mapping between stories, bugs, test cases, and test cycles.

The traceability mapping feature is something that became very useful, especially during releases and bug fixes.

The creation of epics and stories/defects is also very useful and simple.

It should have its own repository for test case creation, so that one does not have to resort to third-party tools and plugins.

JIRA is the project management system in my company. We use it on a daily basis. It is the main instrument widely used by QAs, Product Developers, Technical Writers, and Project Managers

All issues are stored in one place. JIRA stores history of changes, which helps a lot to track who, when, and why the issue was modified. Also, JIRA is very customizable, for example, you can add unique fields or remove the existing ones. Reports, analytics, and a ton of widgets, they are great and intuitive. Perfect for an agile team.

1. History of changes/activities
2. Customizable path of changing statuses of issues
3. Ability to limit access rights
4. Integration with other tools

As a Technical Writer, I would love to have more features to make nice documents, like Release Notes or a feature overview, right from JIRA.

For QA, the most interesting for me are boards, backlog, and filters.

We finally started to use Git integration, so it is easy now to find a fix of a specific issue.

Filters: I never use a simple filter because it is not enough. When I have a complex filter and switch to simple, the switch is impossible. Also, even with complex filters, not all searches are possible.

Grid: It is really strange that there is no possibility to edit an item in the grid. You need to go inside, and even then, not all items are editable, so you need to switch to edit mode. That's too many clicks and switches.

Make the product more user-friendly. It should be easy even for a person on his first day: to edit items, to select several items, to copy items. The product should be for people.

Two years.

Not yet.

Not yet.

Haven't used it.

Yes, I've used HPE Agile Manager. I switched because I switched the company I work for, and the new one works with JIRA.

I didn't install it, I only use the web interface.

Not my area of responsibility.

Not my area of responsibility.

One of the valuable features is traceability from requirements to test cases.

Traceability was not available before. This is a great advantage for audits

I would like to see test execution modules.

We have used this solution for three years.

We encountered only a few issues with stability.

We did not encounter any issues with scalability.

Technical support is good. We use Beecom as the provider.

QC was used here, but I do not know why they made the switch.

JIRA can be parametrized quite intensively. Once you understood how it works, it works well.

We started here with this product, after the decision was made.

Use Beecom as the provider.