Reviews (1-25 of 100)
- JIRA Query Language - simple and extremely powerful search for issues.
- User and group management - To manage multiple teams and users is very simple as well.
- Webhooks and ready to use third party integrations like Slack keeps everyone informed about project updates.
- JIRA project work dashboards are very useful and we use it to display on a kiosk where entire team can keep track of issues.
- JIRA gives multiple ready to use project types and customisable issue workflow.
- Promotes Agile methodology
- UI performance can be improved. It still feels slow even after 5 years of using it.
- They could've offered Confluence along with JIRA since it's not reasonable to pay for project documentation separately. We simply use Google docs for that purpose and it's free!
- There is a steep learning curve for tech and non-tech users initially.
- It's mobile support is still very limited!
- The high level of customization on this Agile system is key to meet different niches and industries. You can configure to use on any project you wish to take on without any effort.
- A system you can learn from. JIRA collects and unites all historic data in a single, searchable hub, and provides access to it at any point of time. This way, team members will be able to perform all sorts of rend analysis and statistical investigations, and prepare constructive reports on their progress.
- A rich toolkit for developers. While it is true that JIRA is mostly appreciated for issue and bug tracking, those are far from being the only features you should know about. This system will become your developers’ favorite assets before you know it.
- The UI is a bit confusing sometimes to the inexperienced user.
- The price can be a little too much for small businesses.
- Too many features, that sometimes can bring some complexity to the platform (this is sometimes rated as a good area too, it will depend on how experienced [you are] and the points you want to cover with this tool).
- When you want a configurable workflow for different issue types
- Showing the entire sprint progress at a glance in the burndown (or burnup) chart
- Ensuring every team member (even a new one) knows the steps that an issue has to take before closure
- Workflows and schemas are sometimes really difficult to understand. You learn it one time and it works fine for 6-7 months. When you need to modify it, it seems you need to learn it ALL OVER again.
- Left hand navigation panels sometimes need to be collapsed and expanded multiple times.
- An effective tool for planning/tracking work from project backlogs and Sprint
- An effective tool for tracking defects
- Fully customizable Kanban and Scrum boards
- Easy to maintain the integration of defects and test using a test management tool like QAComplete.
- JIRA is fully customizable, although we were able to make our QA process fit into JIRA's workflow, it is not designed to work like this. Not easy to make it work as a test management tool.
- Great tool for agile development
- Allows flexibility to build out workflows that map to your company's internal processes
- Flexibly reporting and build out by team
- Make certain the full end to end processes are documented - changing flows will impact the lineage of your data
- Make certain someone on the team has JIRA experience or have a vendor support you in the implementation
- Look at full functions offered out of the box and understand additional plug-ins that may be needed.
- Tracking projects based on assignee (ie: the person who needs to take action on a ticket).
- Easily seeing how many product tickets are open at any given time.
- Planning and road mapping of your product, Jira makes it very easy to track priority with development effort, you can display it easily on a map.
- I'd like to see merge fields be slightly easier to use, but you can still format everything really nicely in comments, so it isn't a big problem.
- Flexible in building interfaces for different teams
- Powerful archive provides historical data for past projects in case they need to be retrieved
- Links to different software to easily load information and build tickets faster
- Interface is outdated and not easy to use, which makes it slower to work with the tool
- Ticket linking is not very flexible, so it's not easy to reference work to other department work in progress or past
- Overall system is very technical, making it challenging for more non-technical teams to join and use the tools
- I personally like the ability to track where issues and task are, how much work has been completed on them and what the estimated time remaining is.
- Easy to interact with a task. Easy to get into the task for the bug fixes and report it to the higher level through the spontaneous notifications.
- I like how JIRA helps teams organize themselves.
- I can't say anything that bothers me about JIRA.
- The price is little bit high.
- Customized workflows - JIRA can be set up to work for any imaginable workflow.
- Fine grained account control - roles can be created for any type of user access, giving you full control.
- Nice looking and easy to use UI.
- Available in SaaS and self hosted.
- It can be overwhelming. So many configurations and options can make it difficult to manage.
- It's among the most expensive in its category. Much cheaper options are available and likely do what you need.
- If your admin configures things wrong, it can be very difficult to use as a user.
- Manages Epics (projects) very well. Tasks can be adjusted easily along with their corresponding Story Points. The Backlog can be easily managed by moving Tasks around as needed.
- Notifications can be automatically sent out (if setup) to the Developer when new work is assigned.
- Epics/Tasks/backlog items can be managed through an easy to use drag and drop process.
- I don't have anything negative to say about the software.
- As with any software, the GUI can always use improvement, but that comes with time.
- JIRA is great for tracking issues
- It allows for excellent communication with other JIRA users
- It's easy to search and navigate the platform
- Administration of JIRA is very easy and straightforward
- Documentation is generally pretty good as is JIRA support
- Sometimes the documentation is a bit tricky to find depending on what version you're running
- Troubleshooting complex issues when you use multiple plugins can be difficult
There are different roles and types of access, so you can define access at a pretty granular level.
- Easy and efficient way to organize and assign work
- Allows for the creation of a hierarchy of tickets and work to keep priorities organized
- User-friendly and cost efficient as an organizational tool
- Training resources readily available
- Being able to create epics would be highly useful for better organization and maintenance
- Being able to split the work, or tickets, between team members would also be useful
- There is a learning curve which does require time and resources to adapt to the tool
- Easy to drag and drop issues to status
- UI is very good and easy to follow the sprint progress
- Dashboard features are good
- Issue detail view can be a little limited, would like more room to configure
- Change the status of issue in all issue views
- Increased functionality on dashboards, allow text field boxes
Excellent for IT production release management, we use a TFS plug in for our code
Works well when paired with Confluence
Works well when paired with Service Desk
Non IT departments have a hard time using it since they don't typically work in agile
- Great for engineers to track issues, bugs, problems, etc.
- Helpful for collaboration on bugs and great for managing sprints.
- Definitely not the prettiest or most intuitive interface. Very much feels like it was built by an engineer.
- My biggest annoyance is that I get emails for updates to a bug's comments far too frequently. As in, someone will be editing a task and I'll get 5 emails in the course of them simply typing something out or making updates to the task. These things should be aggregated and there should be a time delay on when the emails reach me.
JIRA Review: "Great for any project that requires collaboration between developers and product managers"
- JIRA is an excellent tool to connect different teams and work styles in an efficient way, without being too specific for some of them.
- It has a lot of features and settings to offer which really enable you to plan a task in a very detailed way.
- Thanks to the different conditions of a task, the status can be tracked easily and everyone always knows who's the one who has to provide input.
- JIRA is not the right tool for people who are looking for an easy, small and quick to learn project management tool.
- There should be more options to layout a task in terms of tables, image integration et cetera. Currently, the bigger a tasks gets, the more complicated and difficult to understand it looks.
In the software development department of the company, we control projects under the agile methodology. We manage all the development and maintenance projects of our internal applications using JIRA. We control development times and assign priorities to projects.
In addition to this, we receive feedback that comes directly as pending issues in Jira of the users, to more efficiently manage the improvements and failure reports of all applications in use and in the process of testing.
- It is excellent for the control of development projects under agile methodology.
- It allows you to reprogram issues, attach images, set subtask to each issue, which later depending on the complexity you can convert into an issue to execute later.
- By closing each sprint you can graphically view the Burndown Chart, which allows you to analyze with the development group, if the sprint was under what was planned or what caused the deviations.
- It would be ideal to have among the notifications one that alerts when a sprint is about to finish and still has tasks to do and in progress.
- The user interface for Jira in the cloud and Jira on server versions should be the same.
- It should have an integration with the Outlook calendar, iCal or any other calendar so that everyone has calendar programming in a single application.
- JIRA does particularly well on tasks and activities tracking.
- It allows users to easily incorporate supporting documents with various formats.
- Easy monitoring and summarizing and is also flexible on assigning and commenting on a task.
- Sometimes the software is unresponsive
- I also experiencing some bug occasionally
- Comments are viewed and order historically, hence it's difficult to have context if commenting on older comments
It provides a good dashboard where higher leadership can look at how things are progressing and ultimately bringing in transparency.
It eliminates the need for individual teams to send weekly or monthly status reports to leadership on progress and what they are involved with. So at team level sprints, stories, epics, sizing, capacity, scrum and Kanban boards are managed and looked at.
- Requirements are managed very well there which can be captured in the form of epics.
- Epics, which capture the high-level ideas can be broken down into stories, tasks and sub-tasks.
- The team can team can raise bugs, capture comments and tag test cases, against each story ultimately bringing end-to-end traceability.
- Since distributed agile requires more collaboration, JIRA's seamless integration with communication tools like HipChat and Slack allows teams to work collaboratively.
- JIRA supports customization since each team is unique, you can create your own issue types, modify the workflows, add/remove fields.
- Standard issue types created in any project are: a) Bug b) Task c) Sub-Task d) Epic e) Support Ticket f) User story
- User Story workflow can be: a) Backlog b) Ready to Start c) Dev In-Progress d) QA In-Progress e) Ready for Demo All these can be modified based on your requirements.
- If you are looking for devops implementation, JIRA has support for CI & CD.
- It can be integrated with Git and Jenkins very well.
- JIRA supports two kinds of boards, Kanban and Scrum boards. It is very easy to track things using these boards & it also provides ample of charts like reporting options such as burndown charts to help teams plan & replan at every stage in the development life cycle
- Searching issues in JIRA is very simple through JQL (Jira Query Language).
- If we would like to perform a complex search JQL allows to find issues from any timeline.
- The basic version of Jira do not have support for test management, capacity management & release management.
- So users have to buy various plugins to support these basic functionalities which can prove costly based on team size.
- Navigation around the UI can be difficult at times
- Jira is not a simple tool, it requires some training before users can start working on it so some learning curve is involved.
Situations where JIRA is helpful:
1) If our board becomes quite dense and full of issues, it can be difficult to remember all of the issue numbers or track them, so in JIRA we have the option to flag and comment on the issues and the ticket background color becomes yellow which makes the tracing quite easy.
2) Prioritization has become a lot easier with JIRA. It is a one-stop shop for all tasks and projects you are working on. It gives a better look into what each program is working on.
3) When a lot of tasks need to be updated, we can use the “Bulk Change” option present in the right-click menu. It is a good time-saving tool when we have more than 8 tasks to change at once.
4) Many filters can be set in JIRA based on the issues you want to track:
a) Quick filter query to see what is currently scheduled to the sprint. Query: Project = "ABC" AND sprint = ‘Sprint number’ AND issuetype in (Story, Bug) ORDER BY issuetype ASC, status ASC
b) Quick filter query to view the backlog items: Query: Project = "ABC" AND Status = "1.1 Backlog" ORDER BY Rank ASC
Situations where JIRA is not helpful:
1) If your stories have lot of architecture diagrams or documentation you need to integrate it with another Atlassian Tool Confluence & Jira do not have much support for excessive documentation.
2) Even after buying the "Test" plugin, test case management is not that easy & extensible as we have in HP ALM or Rally.
- It is a well-known and recognized issue tracking tool.
- It is extremely customizable, both in terms of customization of the tickets themselves as well as how one can apply workflows to manage your process.
- Given its wide usage in the market, there are a number of 3rd party plugins/integrations available for JIRA; you can tie it to your repository and have an integrated view of development within the issue tracking tool (for example).
- Atlassian recently made a number of UI changes to both JIRA and Confluence. The Confluence changes negatively impact productivity by hampering what used to be a relatively straightforward navigation process. JIRA received an analogous set of changes; while less egregious, I find the new look increases my eye strain when trying to find needed information. New users may not have as much difficulty, but you should try it for yourself.
- Atlassian offers both a Cloud and on-premise solution; the Cloud version doesn't offer many customizations and plugins that are present on the on-prem (server) version.
- The amount of customization offered by JIRA is a blessing and a curse. Generally speaking, it's important to keep things as simple as possible; avoid adding custom fields or super involved workflows as much as possible (though the default workflow doesn't work in most situations based upon my experience).
- You'll need to nominate someone in your organization to own the JIRA effort -- this person should have a reasonable knowledge of JIRA administration but also have the ability to fairly present options and solutions as issues arise. If you don't have someone in this org but opt for a committee of sorts your instance can become a true mess and will negatively impact productivity.
JIRA Scorecard Summary
JIRA Technical Details