Jira
AtlassianReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
7,109 reviews
from
External reviews are not included in the AWS star rating for the product.
For Software Dev
What do you like best about the product?
ease of collaboration. ability to integrate with other applications. quick to learn
What do you dislike about the product?
on prem version has been configured incorrectly -easy to configure badly
What problems is the product solving and how is that benefiting you?
agile adoption
overall this is a useful tool for project management
What do you like best about the product?
I like the ability to tag team members and they will get email alerts even if they are not signed into Jira (unless they've unsubscribed)
What do you dislike about the product?
it seems difficult to visually show timelines. Example: if one team member misses due date, what does this do to the overall timeline for the project?
What problems is the product solving and how is that benefiting you?
we have solved a communication issue in our business and have seen the benefit on project management and delegating tasks
Jira, workflow for scrum and mor
What do you like best about the product?
Easy way to have groups work together on software systems with minimal disruptions.
What do you dislike about the product?
Some people do not update status and tickets can lag without updates.
What problems is the product solving and how is that benefiting you?
Management of aigle software evelopment.
Recommendations to others considering the product:
Start slow with one board than add as org grows.
Great System
What do you like best about the product?
There are lots of potential features and ways to customize, great at keeping track of where the project stands.
What do you dislike about the product?
Visual layout could be improved; appears to be slightly outdated.
What problems is the product solving and how is that benefiting you?
We use Jira as the management tool between our company and outside developers. It is a great way to organize their lists and keep tabs on what they are working.
Recommendations to others considering the product:
Get organizing software.
Using JIRA for updating daily status of work done
What do you like best about the product?
The GUI is very user friendly. I have not followed any guide to use JIRA for following:
1) Create a task and add required description, tentative completion date, daily status, hours logged, assign it to others in team.
2) Create a story, add respective sub-tasks, detailed comments per story/ sub-task, sprint it it tagged to, story points, tentative end date, start/stop progress, assign it to others in team.
3) Raise a bug and monitor its progress.
1) Create a task and add required description, tentative completion date, daily status, hours logged, assign it to others in team.
2) Create a story, add respective sub-tasks, detailed comments per story/ sub-task, sprint it it tagged to, story points, tentative end date, start/stop progress, assign it to others in team.
3) Raise a bug and monitor its progress.
What do you dislike about the product?
Sometimes, the comments are added successfully but it still gives error stating there was some error while updating your comment but once you refresh it, you can see the comment right there.
What problems is the product solving and how is that benefiting you?
It is really very helpful in tracking the overall progress of project.
One can configure the dashboard in a way to simply check how many tasks, stories, sub-tasks, bugs are assigned to individual in a team, what is the progress of each task, what tasks have been started, how many hours have been logged per day etc. Also, can generate graphs, reports stating overall progress of current sprint, burn downs, blockers etc.
One can configure the dashboard in a way to simply check how many tasks, stories, sub-tasks, bugs are assigned to individual in a team, what is the progress of each task, what tasks have been started, how many hours have been logged per day etc. Also, can generate graphs, reports stating overall progress of current sprint, burn downs, blockers etc.
Full featured issue tracking and roadmap tool for product support and management
What do you like best about the product?
Easy to create tickets, add attachments, and track history. Easy to create links to specific entries within a given Jira ticket.
What do you dislike about the product?
Nothing in particular. It is sufficient for software development teams.
What problems is the product solving and how is that benefiting you?
Tracking bugs, planning for future releases
Using Jira to track bugs and plan sprints
What do you like best about the product?
it is easy to use and have a lot of features. Very well integrated with other tools like git.
What do you dislike about the product?
UI can be improved a lot. Difficult to search for some of the bugs using text.
What problems is the product solving and how is that benefiting you?
Tracking bugs issued to users and also helps in sprint planning
Recommendations to others considering the product:
Yes, I recommend others to use this product.
Lead product manager
What do you like best about the product?
As a lead product manager, I like the fact that JIRA lets me collaborate with my engineering team in an effective manner. We use JIRA to track all sprint deliverables including monitoring progress and engaging across the team by posting questions and answers, updates and clarifications related to particular requirements. I also use JIRA to pull reports to check the statuses of key deliverables. In a prior role, I was also a product owner and used JIRA to build out my roadmap and maintain a clean sprint backlog. I also leveraged reports to measure team velocity.
What do you dislike about the product?
JIRA has not been an effective tool to engage user experience (UX) in the dev process. As a lead in building out consumer facing web products, it's critical that UX and engineering have a way to interact. Today, our UX team uses Invision to create mocks and prototypes, which need to tie back into the JIRA for dev team to reference. However, there is a disconnect with integrating these processes and as a result, either I (or UX) need to copy+paste screenshots into JIRA, or link back to the Invision project (outside of JIRA). Ideally, JIRA would help in this type of collaboration. It's possible they have a solution, but it's not obvious to me.
What problems is the product solving and how is that benefiting you?
In my role, I'm focused on building out features that allow us to scale in the enterprise and features aimed at optimizing key Marketo workflows. My work spans across the platform and application side of the house. This means I'm collaborating with a different set of actors and JIRA plays a critical role in my ability to manage multiple unrelated-projects with different groups of engineers.
Recommendations to others considering the product:
I belive JIRA can address numerous use cases. I encourage you to get familiar with the tool and work with your broader team to organize your instance in a way that makes sense and maps to your engineering organization.
Great way to organize IT Requests, Bugs, and Creative All in one
What do you like best about the product?
We have automated JIRA tickets being created when we need IT help, creative needs, or to even submit bugs. This makes my life so easy when trying to organize and identify where in the process my tickets are.
What do you dislike about the product?
Sometimes it is difficult to find tickets vs bugs vs creative requests. I would love to easily identify these just in one screen. Almost like my own personal newsfeed.
What problems is the product solving and how is that benefiting you?
Organizing and streamlining requests. Additionally we're able to document the historical bugs to ensure we learn and apply the next time we release another product.
Team Request Queue Management
What do you like best about the product?
Ability to watch, or partially comment a ticket to select audiences without having to be a ticket requester or owner.
What do you dislike about the product?
I find the ability to leverage the API or schema really difficult to import into other reporting softwares.
What problems is the product solving and how is that benefiting you?
Team ticket management and springplanning
Recommendations to others considering the product:
Think about if you want to use Jira in the UI or import elsewhere. Less technical users may have trouble but easy use for technical teams.
showing 6,941 - 6,950