Jira
AtlassianReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
7,110 reviews
from
External reviews are not included in the AWS star rating for the product.
Great Commercial Issue Tracker and Agile Product Management Tool
What do you like best about the product?
Easy way to combine bug tracking with requirement management. I started using JIRA 5 years ago only for issue tracking and linked it to my QMetry Test Management software. Back then they had an agile plugin called "Greenhopper" which was nice, but not yet fully integrated. A few years back Atlassian bought Greenhopper and rebranded it as "JIRA Agile" and we started using it for product planning. What I really liked about this was my ability as a product manager to see what was in development and to track the progress of both development and QA.
Permissions
Since a lot of people use JIRA for competing purposes it is important to have tight control on permissions. JIRA provides that. To be honest 5 years ago the Admin was very confusing, but it has gotten much better as the years have progressed. What is clear is that the control is very good. We have over 50 separate projects now with over 500 users. Some projects require strict security, others are shared between users. We use a combination of AD groups and our own custom groups to assign permissions.
Workflows
We could probably do more here, but we have played around with workflows and got a lot of benefit out of it.
Permissions
Since a lot of people use JIRA for competing purposes it is important to have tight control on permissions. JIRA provides that. To be honest 5 years ago the Admin was very confusing, but it has gotten much better as the years have progressed. What is clear is that the control is very good. We have over 50 separate projects now with over 500 users. Some projects require strict security, others are shared between users. We use a combination of AD groups and our own custom groups to assign permissions.
Workflows
We could probably do more here, but we have played around with workflows and got a lot of benefit out of it.
What do you dislike about the product?
The Agile board often crashes. This is caused due to a fairly large backlog, but a backlog I feel is well within reason based on my experience.
Custom fields have been a source of pain. Fields are shared between projects and with a seemingly unlimited number of UDFs we have a lot. It is not uncommon for a new field to crop up in an existing project. Sometimes it is even mandatory! I think this is largely just bad administration, but having done a bit of admin for the tool myself I can say it was not always intuitive. Thankfully I feel it is getting better.
Emails- way too many! You can turn off emails, but I don't want to do that. I want emails I just don't want too many. JIRA made it so that developers could quickly make updates for each field rather than opening an edit window. Sounds good, right? In practice it sucks. Many days I get over 100 emails relating to just a handful of issues. Worse Outlook doesn't group the emails! Sifting through the emails to find the relevant ones is a time suck.
Custom fields have been a source of pain. Fields are shared between projects and with a seemingly unlimited number of UDFs we have a lot. It is not uncommon for a new field to crop up in an existing project. Sometimes it is even mandatory! I think this is largely just bad administration, but having done a bit of admin for the tool myself I can say it was not always intuitive. Thankfully I feel it is getting better.
Emails- way too many! You can turn off emails, but I don't want to do that. I want emails I just don't want too many. JIRA made it so that developers could quickly make updates for each field rather than opening an edit window. Sounds good, right? In practice it sucks. Many days I get over 100 emails relating to just a handful of issues. Worse Outlook doesn't group the emails! Sifting through the emails to find the relevant ones is a time suck.
What problems is the product solving and how is that benefiting you?
Requirement Tracking
In the past I often had to write Product Requirement Documents (PRDs) which were usually outdated as soon as they were printed. What made matters worse is the engineering often didn't reference the PRD once development started, and a few times QA never even saw the original doc. They would pass or fail features without really knowing the user story. And if they failed something engineering often said it was "as designed". Without anything to disagree with that statement the feature would often be passed and I would end up catching it late in the process- sometimes too late.
We moved our requirements to JIRA 5 years ago and eliminated the above problem. The comments in JIRA keep communication clear between all groups. Comments can be in rich text and can included pictures and mockups.
Agile Development
A couple of years ago development fully embraced Agile using the JIRA Agile add on. This improved communication in development and kept us on schedule. The most significant thing was using the ranking on the Agile boards to prioritize development. This was a game changer. Very easy to do.
In the past I often had to write Product Requirement Documents (PRDs) which were usually outdated as soon as they were printed. What made matters worse is the engineering often didn't reference the PRD once development started, and a few times QA never even saw the original doc. They would pass or fail features without really knowing the user story. And if they failed something engineering often said it was "as designed". Without anything to disagree with that statement the feature would often be passed and I would end up catching it late in the process- sometimes too late.
We moved our requirements to JIRA 5 years ago and eliminated the above problem. The comments in JIRA keep communication clear between all groups. Comments can be in rich text and can included pictures and mockups.
Agile Development
A couple of years ago development fully embraced Agile using the JIRA Agile add on. This improved communication in development and kept us on schedule. The most significant thing was using the ranking on the Agile boards to prioritize development. This was a game changer. Very easy to do.
Recommendations to others considering the product:
If you are not sure if JIRA is right for you then spend $10 to get a 10 license copy. Use that with one project and see how it goes.
Senior Software Engineer, Jira is great and integrates well with other dev tools.
What do you like best about the product?
The link to Confluence(Wiki), BitBucket(Git repo), and the ability to link tickets.
What do you dislike about the product?
I have never tried outside integrations such as Jira to GitLab. I would like Jira more if it worked with Git Repos or CI tools outside of Atlassian's universe.
What problems is the product solving and how is that benefiting you?
Moving forward software development quickly and efficiently and collaborating with Project Managers, Managers, and Engineers.
JIRA- PM and data collection
What do you like best about the product?
The interface is easy to use, clean, and simple. Automatic email notifications once ta task has been assigned are also great,
What do you dislike about the product?
Reassign/Reopen features seem a bit redundant.
What problems is the product solving and how is that benefiting you?
We needed a PM tool that could be easily implemented and was cost effective. The SW engineering team already had licenses, so we set up our Team as a JIRA project. All tasks are now visible to the entire team and we can collect data passively.
Recommendations to others considering the product:
This tool helped my team stay aligned and consistent by following pre-designed workflows for each service we provide to the engineering team. We always know what's due and how long things take. It makes our team meetings more efficient,
Intuitive
What do you like best about the product?
It's easy to customize per project/vertical. It's intuitive to direct your questions to a specific person for each issue.
What do you dislike about the product?
Expensive for daily use. there are certain features that are hard to find without having prior training.
What problems is the product solving and how is that benefiting you?
It is mainly useful for assigning tasks to specific people and has transparency on the progress of each task.
very good
What do you like best about the product?
clear architecture and easy use to manage projects
What do you dislike about the product?
little too much features, can be little bit confusing.
What problems is the product solving and how is that benefiting you?
We solve our project managements benefits with it.
Great System
What do you like best about the product?
It's easy for us to choose where a ticket goes and getting email updates on the progress makes it so we don't forget that it's there. I like knowing exactly when something has been resolved as well.
What do you dislike about the product?
Nothing at the moment. Works fine for what I need.
What problems is the product solving and how is that benefiting you?
Mostly issues within our internal programs.
Productive project management tool
What do you like best about the product?
The interface is easy to face and allows me to keep tasks organized.
What do you dislike about the product?
Having to drag tasks from sprint to sprint can be tedious
What problems is the product solving and how is that benefiting you?
Increased productivity and efficiency in completing tasks in a timely manner. It also keeps the dev team focused on their priorities.
Pretty decent
What do you like best about the product?
Has a lot of features and customizability that can fit to a business' needs.
What do you dislike about the product?
Takes time and knowledge to figure out how to set it up to be useful for what is its needed.
What problems is the product solving and how is that benefiting you?
Project Management software using agile process. Works fine if set up correctly.
Not the most intuitive
What do you like best about the product?
The feature my team likes best is the ability to attach a pull request to a ticket. That's the main reason we use it. This is obviously most valuable to the project manager and developers, but it's nice to be able to follow along with the team so I can make sure my styling changes are implemented.
What do you dislike about the product?
Unfortunately, there is a bit of a learning curve when using Jira. As a designer, I definitely prefer other project management tools because the UX is confusing and it seems like an overload of information. Jira isn't very intuitive and doesn't really offer any tooltips to help learn how to use it. Because of this, we have to Google how to do many things. It really takes some getting used to if you're more of a visual person than a technical person.
What problems is the product solving and how is that benefiting you?
Like I stated above, we use Jira primarily because of the ability to tag a pull request on a ticket, that way if something goes wrong, we can easily pinpoint where it happened and fix it. We weren't able to do this with Trello, so we switched to Jira. All of the development teams are now using Jira where I work and it's nice if you switch teams to already be used to the same workflow as everyone else.
Recommendations to others considering the product:
Don't get frustrated and give up if you're used to something similar like Trello. Once you get the hang of it, it's pretty easy to use. You just have to get past that learning curve.
Migrating from a solution that was chaos to a solution bringing harmony.
What do you like best about the product?
The ability to not only view the work being completed but also the ability to assign tasks to multiple resources all at once and have the capability to collaborate during the entire session with a chat log.
What do you dislike about the product?
If you are unfamiliar with Atlassian you might have a difficult time navigating around the tool. You may experience issues when trying to create stories and assign out the tasks assigned to those stories. Confusing jargon already right?
What problems is the product solving and how is that benefiting you?
The ability to not only track work but to ensure the work being completed remains on time and on schedule. If there are bumps in the road you have the ability to update the timeline real-time.
showing 6,761 - 6,770