- 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.
- 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.
- 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 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 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.
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.
- Task Management - Keep Track of Tasks
- Priority Management - Prioritize Tasks
- Reporting - Create Reports That YOU Need
- Customization - Better customization for specific needs
- Ease of Access - More training or helpful tips within the program
JIRA Review: "Great for agile teams and development work coordination, but reporting could use some work"
- Fits right into agile methodology and very easy to use.
- No problems with copy/pasting images, attachments, and formatting stories to look right. Interface is fast, pleasing to use.
- Commenting and tracking conversation and notes on stories is very easy.
- Reporting and some charting capabilities is lacking. Need better ways to track burndown, velocity, etc.
- Missing functionality for tracking testing and pass/fail.
- A good example of "you get what you put in". It can get messy and overwhelming easily if left unchecked. Some tools and study on this would be helpful to guide users on proper management of agile.
- It helps in Release Management in our rapid release cycles. sync with Product Management tool and Customer support tools.
- Supports various kind Of Agile models like scrum & Kanban
- User accesses, custom story types, Workflow support to automate development cycle.
- I think they can improve on reporting capabilities to get more insights about developer productivity.
- Documentation attached to each story is not readable for non-developer teams. If features were better readable UI/UX for business users will help to get all stakeholders in product process to start using JIRA
- It's great for holding all our projects and tickets with teams assigned.
- It has good features for formatting ticket descriptions and comments for team collaboration.
- I like the hours tracking feature because it's easy to enter hours for each ticket and also see all my time for the week at a glance.
- Better formatting options in tickets.
- Apply UX principles for easier workflow and UI.
- More options to simplify and cut out unnecessary features that we don't use.
- Allows us to customize our board to match the teams' workflows and not the other way around.
- Allows transparency to management and other interested parties.
- If used appropriately it can help cut down on process bloat.
- It can be complicated to set up and manage. Depending on the size of your organization it could require a full time administrator to manage.
- 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
We use it to track all defect discovery, investigation, implementation and retest. We also use it as a way to facilitate discussion of the defects, and determine priority and resource assignment across the organization.
Furthermore, its ability to generate reports and dashboards that are accessible, usable and understandable to C-Suite executives is a great tool to keep our engineers focused on solving defects, and letting the tool handle the reporting side of things.
- Its ability to generate reports and dashboards that are accessible, usable and understandable to C-Suite executives
- Its ability to integrate with other tools through the use of plugins and add-ons (including source code repositories, a big one for use)
- Its ease of use - new hires don't generally need to be trained at all, they pick up the right way to use the tool within their first week
- Some reporting needs the ability to be more customized. For certain reports, we still have to export data to Excel...which is a hassle
- Some features are very software development-centric. We use JIRA to track hardware and software defects, and some of the hardware defect tracking feels shoehorned in
- The default behavior is to email any user tracking a defect when anything happens. In addition, users get added to the tracking list when they perform any actions on the defect. These two combined means that many users get overloaded with JIRA emails
- Organization and prioritization of work
- The ability to customize (forms, workflows, etc.)
- The ability to share information easily (adding attachments, adding "watchers" to issues, as well as integrations with other products)
- The ability to share workflows across projects gets really messy when you want to change one but not the other. You can end up messing up other people's boards without realizing it. It really requires someone who is familiar with the rules of the software to manage things like this.
- Board configuration is a bit confusing as someone can be an admin on a board but if they do not own the board filter they can not share the board with new people. Visibility to a board is based on the board's filter shares which is just confusing.
- It would be nice to have more flexibility with workflows. Often times our product managers ask me if they can add a step in their team's workflow and I have to say no because it would affect everyone else who is in the project. I'm not sure why we didn't decide to give each PM their own project... it might be due to their pricing model.
JIRA Review: "Great for any project that requires collaboration between developers and product managers"
- It has a lot of flexibility in the way you can create swimlanes, flag cards, and move things around on the board.
- Easy to track and follow your team's progress and see if you are getting things done according to schedule.
- The circles that represent the days along the bottom of each card are nice so that you can see if anything is getting stale.
- It needs a better way to auto refresh. Having to refresh the page sometimes can be frustrating.
- Sometimes it's very slow to reflect that you are dragging things between columns, and before you know it you have grabbed the wrong card.
JIRA Scorecard Summary
JIRA Technical Details