Jira Reviews

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.

The adaptability of the Scrum and Kanban boards for other uses, with careful use of the customization features.

It has simplified our PM work tremendously, as we switched from VersionOne. We have much more buy-in from dev teams and we see a marked difference in productivity.

Ease of administration and customization. It is really clunky in this area. Also, permissions are nice, but they need more refinement so a project admin has more capability and less reliance on the system administrators.

We have been using this solution for approximately four years.

There were issues with deployment. Because we use it on-premises rather than in the cloud, for regulatory reasons, we are often behind, but not for long. Apart from that, our PlatOps team always runs into problems, though I cannot speak directly to those issues.

There weren't terrible issues with stability, but it is easy, when customizing, to make a mistake that will "break" JIRA for all users. It takes a lot of care.

I did not encounter any issues with scalability.

Customer service is excellent, although they are only available via email.

Technical support is excellent, because they are responsive.

We used VersionOne and it was simply too powerful, so to speak. It was bulky, expensive, and simply became a mess with so many users. VersionOne isn't a bad product at all, but our IT department just isn't big or complex enough for an "enterprise" product.

We implemented it ourselves.

Our ROI is very good. Almost all licenses are taken and it is even being used by the rest of the business, outside of IT.

The licensing model is annoying. They nickel and dime you.

We evaluated Asana and even Trello, as we were trying to simplify. But those solutions, among others, were too simple.

Ensure that your admins learn by first installing to a QA server for experimentation, if you are doing it on-premises. As for those learning it in the cloud version, create dummy projects, categorize them as such, and be careful about how many changes you make at once.

The configurable workflows and boards make it easy for us to execute and oversee our own unique process. The portfolio feature allows you to conceptualize your roadmap and experiment with various scenarios before committing to execute. Once you learn how to configure the system, it is extremely powerful.

JIRA has created visibility for our IT organization that did not previously exist.

There are some minor quirks, such as zero-point stories not appearing in the portfolio scope. We often poke stories at zero points because we have a very small group that needs outside help from time-to-time. We need to track these stories without impacting team velocity, so we poke them at zero.

These stories will not appear in the scope/schedule in the portfolio because the system interprets zero points as zero scope, even though the issues are open, assigned to the release and assigned to a Sprint. It would be nice to be able to see them in the schedule.

We have been using this product for three years.

We did not encounter any issues with stability.

We did not encounter any issues with scalability.

I would give technical support a rating of 5/10. I have only asked two questions in the support forums. One was answered very quickly and the other was never answered.

I previously used CA Agile (a.k.a. ‘Rally’). My company decided to switch to JIRA because we were already using it for bug tracking. Once the Agile/Portfolio features were released, we decided to use JIRA for all IT project planning and tracking.

The initial setup was pretty straightforward. One thing I personally don’t like is how the system, by default, assumes that all projects will have a different workflow and screen configuration. This adds complexity in my opinion. It should assume that there is a default workflow and configuration across projects and then allow you to copy and customize the defaults.

It is very cheap if you forego the local instance and stick to the cloud.

We evaluated Microsoft TFS and Targetprocess. Neither had a Portfolio planning feature, which is why we decided to stick with JIRA.

Establish a basic project management methodology and workflow first, with clear roles and responsibilities, and then use this product to execute. It is only as effective as you are disciplined in your sprint planning and execution.

Perfect for keeping track of large amounts of bugs, tasks queries and releases for fixes. 

The SaaS does the job it is supposed to: helps you keep track of your projects. What I like most is the ease of adding users and the obvious nature of what they need to do -  drag and drop is always a win. 

It is cross methodology so Scrum, Kanban... it doesn't matter, you can use JIRA.

I like how it shows the sprints remaining. Being able to instantly see where you are in a project and what is coming up is invaluable. 

Also, the ability to link a programme of projects is very helpful. I can see where all of the teams are with their individual projects but also how they fit into the overarching business plan for the year.

In reality, it's allowed me to raise and keep track of 700 tickets (bugs, queries, tasks etc) effectively. I can track what tickets are in UAT and which ones are coming out in the next software release. It's very simple. 

It allows all of those involved in a project, to see what stage their deliverables are (depending on what you allow people to view, they can see all deliverables from all teams)

Keeping everything in one central place with it obvious as to who is responsible for what, is a fantastic thing. 

It gives programme managers an overview of how a slew of projects are going. This also provides information for Exec meetings/Board meetings - visuals are always helpful to instantly show people what is happening with a programme of improvements.

Basically it allows me to see what is happening very quickly. 

I have no areas of improvement that I would push. JIRA does what I need - it allows me to assign tasks and to update my project. Any problems that I have found have been more to do with people entering with a lack of details - rubbish in = rubbish out. But that is the same with all apps.

I've used JIRA for over a couple of years, in three organisations, so I have some experience of how different places use it.

SaaS so nothing to deploy really. 

There's been the odd amount of JIRA downtime (not self hosted) and sometimes tickets that can't be accessed. 

I've not had need to contact the customer support team so I suppose that is a good thing.