Best tool for Project Tracking
In our day-to-day operations, we delve into the intricate world of development, and Jira Software becomes our crucial ally in keeping all …
Starting at $81.85 per month 10 users
View PricingOverview
What is Jira Software?
Jira Software is a project management tool from Atlassian, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Reviewer Pros & Cons
Pricing
Standard
$8.15
Cloud
per month per user (minimum 10)
Premium
$16
Cloud
per month per user (minimum 10)
Data Center
$44,000
On Premise
per year 500 users
Entry-level set up fee?
- No setup fee
For the latest information on pricing, visithttps://www.atlassian.com/software/jira…
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Starting price (does not include set up fee)
- $81.85 per month 10 users
Product Demos
JIRA Project Management Tutorial for Beginners (2022)
YouTube
The full overview: Roadmaps in Jira Software
YouTube
Product Details
- About
- Integrations
- Competitors
- Tech Details
- FAQs
What is Jira Software?
Jira Software is a project management tool software used by agile teams and supports any agile methodology, be it scrum, kanban, or a team's own unique flavor. From agile boards to reports, users can plan, track, and manage agile software development projects. And since not every team works the same way, Jira Software allows teams to customize workflows, permissions, and schemes to match the unique needs of each team.
Jira templates also support use cases in enterprise marketing management, and projects to support operations, design HR, and enterprise marketing management.
With Jira Software, teams are able to:
- Track versions, features, and progress at a glance
- Re-prioritize user stories and bugs
- Estimate stories, adjust sprint scope, check velocity, and re-prioritize issues
- Estimate, track and report on story points; become more accurate
- Report on agile metrics to provide real-time, actionable data on team efficiency, quality, and overall performance
- Integrate with all the tools their dev team is already using, from the rest of the Atlassian suite (Bitbucket, Bamboo, Fisheye, and Crucible) to other popular developer tools on-premise or cloud (e.g., GitHub and Jenkins).
- Provide greater flexibility to curate which teams have access to which information with sprint and project-level permissions
- Flexibly tailor Jira tasks and their workflows to a specific team's use case
- Extend Jira with over 1,800 apps from the Atlassian Marketplace to fit any capability not provided by default
Jira Software Videos
Jira in a Nutshell Demo Video
Jira Software is a software development project management tool of sorts, that tracks progress, offers up project reports, and gives a great roadmap view to understand workloads and deadlines better. In this video, the TrustRadius team goes over Jira Software pricing, top feat...
Show More Jira Software Integrations
Jira Software Competitors
Jira Software Technical Details
| Deployment Types | On-premise, Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Windows, Mac |
| Mobile Application | Apple iOS, Android |
Frequently Asked Questions
Jira Software is a project management tool from Atlassian, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
Jira Software starts at $81.85.
Reviewers rate Support Rating highest, with a score of 8.8.
The most common users of Jira Software are from Enterprises (1,001+ employees).
Comparisons
Compare with
Reviews and Ratings
(3245)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Pros
- Cons
Easy-to-use tool with minimal learning curve: Users have found JIRA to be an intuitive and user-friendly tool that requires minimal effort to learn. Several reviewers mentioned that they were able to navigate through the platform easily and quickly adapt to its features.
Seamless collaboration through integration with other tools: Many users appreciated JIRA's ability to integrate with various plugins and add-ons, enabling seamless collaboration across different teams and departments. This integration allowed for enhanced productivity by bringing together different tools into one centralized platform.
Flexibility of customization: The flexibility of JIRA in terms of customization was highly regarded by users. They mentioned being able to customize bugs, tasks, and stories based on the specific requirements of their projects. This flexibility helped them tailor JIRA to their unique project management needs.
Confusing and overwhelming user interface: Many users have expressed frustration with the confusing and overwhelming user interface of JIRA. They find it difficult to efficiently complete tasks due to a lack of intuitive navigation and cluttered design.
Complexity and difficulty in customization: A significant number of reviewers find JIRA's customization options to be complex and challenging. It often requires dedicated training to effectively navigate and utilize the software's customization features.
Limitations in reports, charts, and attachments: Users have reported challenges in sharing information within JIRA due to limitations in reports, charts, and attachments. These limitations hinder effective collaboration, communication, and data visualization.
Attribute Ratings
Reviews
(151-175 of 188)Companies can't remove reviews or game the system. Here's why
April 27, 2016
JIRA, at the forefront of the industry.
We use JIRA in conjunction with our partner. During our prototype design phase we use it to track any issues encountered by either party. It is also used during a products life cycle should any problems be found by customers or if redesigns are necessary. JIRA is used exclusively by one department in our company. It addresses the need for transparency and communication between the necessary developers.
- Issue tracking.
- Project management.
- Variable workflows.
- High learning curve.
- Not viable for certain types of development.
- "Clunky" user interface.
April 18, 2016
Quick Atlassian JIRA review
JIRA Software is used for tracking bugs, enhancement requests, and development of tasks/sub tasks.
- Ability to set customized processes/workflows.
- Ability to integrate other tools, such as Testrails and Jenkins, and send notifications via email or IM programs.
- Still learning about JIRA and have not found any big holes or missing functionality.
April 05, 2016
Review from an account manager's perspective
JIRA Software is used by the digital team to track and monitor defects during the QA process of a project. This typically includes the account team as well as developers, and often times clients. It's a fairly user friendly tool that allows us to streamline communication with real-time execution and monitoring.
- Tracking tasks and defects for web projects during development + QA phases.
- Though JIRA makes it really easy to track communication, it also has some difficulties. There are often so many drop downs and fields to fill out, that sometimes it almost seems like a circular experience. I know it is customizable, so this is likely just a user-issue by our internal teams. :)
March 08, 2016
Great for a small team, potential for a large one
As a small software startup, we use JIRA to manage our development pipeline. We log development ideas in the platform, identify priorities, communicate regarding developments and clarification, and keep track of what's been implemented. We're currently maintaining one version of our software while developing a completely new version from scratch to be launched later this year. JIRA helps us keep track of the priorities and projects regarding both of these development tracks.
- Helping you prioritize; you can determine the estimated time for a project, score them by business value, and organize them into different categories.
- Communication; comments on tickets are emailed to the person who created them, so it's easy to maintain a back and forth conversation without having to have meetings or send emails.
- Planning multiple projects at once; it's hard to keep track of tickets when developing multiple versions of software, but JIRA makes it easy by allowing you to set up different projects and rank tickets in each one independently of the others.
- The sync between JIRA and Zendesk's support site could be better.
- JIRA has a great UI, but some clicks could be reduced in some areas by allowing lists to be editable without having to actually go into the tickets.
- Email notifications can be overwhelming if a developer is plowing through a list of your tickets. Would be better if JIRA sent an update summary email every hour or so, instead of an update for each ticket.
March 08, 2016
I'm a fan!
JIRA was used by our software development organization as the one true source for what work needed to be done, when and by whom. Although our approach was generally waterfall with some agile-esque concepts mixed in, JIRA proved to be a powerful tool for us. We created an extensive JIRA workflow to track and manage portions of our development projects from idea, design & requirements, development, QA, tech writing, UAT, etc. We also made extensive use of the dashboards to provide transparency to individual contributors and stakeholders alike.
- The biggest impact from experience with JIRA is the transformation it took from when I first started using it, until now. It seemed like the good folks at JIRA really practiced what they preached and I reaped the benefits. When I first started using the agile boards, it was at a time when they had just come out with a new version if you will and were sunsetting the old version (I can't remember the names). Anyhow, the agile board worked enough for me to check the box that I had a backlog. It did the basics. As time went on however, I was thoroughly impressed at the features that they added. It was as if they had been sitting at my desk alongside me and noticing my frustrations and then fixing them.
- Other favorite features, dashboards, saved searches, workflow, labels, advanced search query, linked issues, follow issue, history, batch updates, view in issue navigator. All these features seriously make life easier when working in JIRA. The administrative headaches of product management are out the window.
- I also dig the administrative features like find my field. This makes it so easy for an administrator to identify the cause of a configuration error and fix/test quickly.
- One thing that ever bothered me about JIRA was the rank feature. It used to be a global rank, so I could I query issues and display them in results by order of priority (rank) regardless of what sprint they were in. Now rank is only applicable in the context of a sprint, which is not so powerful really if I want to prioritize across several teams regardless of sprint.
- It would be nice to batch update labels, and not have the "all or nothing" approach. At least they have keyboard shortcuts that make updating many issues one at a time a total breeze.
- At my new company, I'm having a hard time converting my peers and management into JIRA admirers. Their concerns are mainly the price and the ease in which the system can be integrated into our homegrown system. Can you make some sort of browser plugin that could compare how long it takes me to complete the same work in JIRA vs my current application?
December 02, 2015
JIRA - not only a bug tracker
Atlassian JIRA is widely used in our organization by almost all departments including Sales, Business Analysis, Product Development, Solution Delivery, Quality Assurance and Customer Support. We have several independent instances of JIRA which are used for different purposes with transparent integration between instances and to and from instances of Atlassian Confluence which is also a highly recommended product.
JIRA is not only a bug tracker in our corporate network but also a task management system for solution delivery, as well as external ticket tracking, task tracking and our requests management system which we use to communicate with customers.
JIRA is not only a bug tracker in our corporate network but also a task management system for solution delivery, as well as external ticket tracking, task tracking and our requests management system which we use to communicate with customers.
- JIRA is a highly customizable tool, almost anything can be adjusted to satisfy various requirements for metrics and charts expected by stakeholders.
- Wide selection of pre-installed tools for reporting allows users to have very useful dashboards for clear data representation (sometimes it's even better that pure Excel with its Pivot Charts).
- Configurable workflow allows us to have separate life cycles for each project, where "Almost Waterflow" is next to Scrum and DevOps.
- While configurable, JIRA requires a certain amount of effort to extend its data schema with new attributes, especially if those attributes need to be calculable or carry some logic behind them - like if you need to calculate the amount of re-opens per ticket throughout the project, it's far from an easy task to do.
- Having quite so many chart options, JIRA still lacks some important ways of data visualization. And there usually comes the almighty "Export to Excel" and Pivots.
- Sometimes it's hard to represent all data points of the lifecycle in the same instance of JIRA, especially when it needs to be done "yesterday" or "abruptly". So we have to use Labels, Components, Fix Versions etc., as anything but what it says just to put everything into the required model of implementation.
October 07, 2015
Pretty good for tracking a lot of work or a lot of people
Score 5 out of 10
Vetted Review
Verified User
Atlassian JIRA is a really powerful tool that we used mostly for bug tracking and customer support tickets. We used it to ensure that nothing fell through the cracks and that we, mostly, met our SLAs. It was phased out over the past year, but for years it was the best solution we had to workflow management.
- Atlassian JIRA has very powerful permission settings so that we can create workgroups with particular access levels to control who saw what information and what they could do with it.
- We used workflow settings to ensure that no steps in the process got skipped and to keep track of who was responsible for every ticket at every step of the process.
- It was a lot of work to administer Atlassian JIRA for a company of just 75 people. It was almost a full-time job for me, which is one of the reasons we changed tools.
- It's not very user-friendly. It took me a few months to start feeling comfortable with the administration settings.
August 19, 2015
JIRA Review - SL
We primarily use the Agile methodology that JIRA offers. We started using it all across the board a couple of months back. Initially it was just the project management team that was using it a few months back. The organization made a decision to use it all across the board and now it is being used by all departments. We use it to track all of our projects, timelines etc.
- Very intuitive tool. Ease of access is the primary reason why I would recommend this tool. Both from a end user's standpoint and administratively
- Comes with a lot of modules for different kinds of business types, structures.
- Very customizable to your individual business needs
- Very well known tool and has great documentation by users and Atlassian
- Customer support is not always as responsive as you would want them to be
- Version upgrades can be handled better.
July 08, 2015
Web development team relying on JIRA
In our company JIRA is used by our Web Development teams. We have teams in multiple locations and need a good project management tool. As an in-house web team, we develop various B2B websites and internally used web based tools. Keeping track of every part of the team is essential. This can be a challenge when working in a global company with teams in different time zones. With JIRA, we are able to create and assign tasks to any team member and be sure that it will be taken care of. Implementing JIRA in our work routine also helped us bring a good and efficient workflow to any type of task.
- Workflows. Being able to define workflows for any type of a task, helps with keeping that task on track. Additionally, you can trigger various actions when a task hits a step in a workflow, like automatically re-assigning a task to a specific team member.
- Dashboards. You can organize your JIRA dashboard any way you want and you can have as many dashboards as needed. This helps when preparing for team meetings and generating reports.
- Customization. Being able to customize JIRA is great. It allowed us to adjust the use of the software to our needs and not the other way around.
- JIRA is missing an iOS app. Even though there is a mobile version of the site, it is not easy to work in. As a manager, I receive a lot of JIRA related emails. Being able to answer questions or make changes on the go would be very helpful.
- You are able to embed a form outside of JIRA that would upon submitting, create a new JIRA task. We use it for submitting tickets. Once a ticket has been closed, there is no automatic way of informing the requester about the resolution.
April 14, 2015
Lead Quality Assurance
Then entire company is using this JIRA and Confluence. Primary reason for switching to JIRA is for Assigning and Monitoring Task assignments and the hours worked using Agile Methodology.
- I like I can easily move a ticket from one project to another.
- I like that I can convert a task to a sub-task and reverse.
- I like that I can link Stories/Tasks . to an Epic.
- I like that I can create a filter and share with team members
- I like that I create a dashboard and share with team members
- I like the comment feature with notification and the tracking of History and transitions for each ticket
- I like that every ticket is a hyperlink, awesome.
- When a subtask is assigned, display parent task/subtask on Work board, both should be clickable.
- Add multiple time logged buckets. For example, one for developers, one for test analyst, one for Business Analyst. Make time logged buckets user defined. This should not have to be an additional purchase, pretty typical in our world today.
April 08, 2015
Atlassian JIRA has significantly improved our work intake and request tracking processes
Our organization uses JIRA for work intake and tracking across multiple departments. It was initially implemented by our Software Development department to manage day-to-day support requests and bug fixes. However, it was so successful that nearly every other department has set up their own project(s) and developed new processes for managing their work intake, centered around JIRA. When used in conjunction with JIRA Agile (it used to be called GreenHopper), JIRA is a fantastic tool for identifying bottlenecks in the process. We use it for work intake, prioritization, tracking, and ultimately as a record of work completion.
- Excellent for use as a repository for work requests
- Allows easy prioritization of work requests
- Can be highly customized to match your processes
- The administrator tools can be difficult to understand - there is a pretty steep learning curve if you want to start customizing
- I wish you could attach a screenshot during issue creation - I don't know why it's available once the issue is created, but not as part of creation
We're using JIRA across the organization to build digital products in Agile with onshore and offshore development teams.
- Planning board allows good visibility into sprints as well as backlog, making it easy to organize and prioritize
- Integration with Confluence allows easy cross-referencing between Product Requirements and User Stories
- Integration with HipChat allows for asynchronous communications across time zones.
- Information Architecture between JIRA and Confluence is abysmal, can be difficult to navigate between the two
- OnDemand instance has limited add-ons.
- HipChat would greatly benefit from a shortcut that links issue numbers directly to tickets
February 25, 2015
JIRA is the bees knees.
At Wonderlic, JIRA is the primary tool used to track requests and projects. JIRA is very popular within the software development cycle (Stakeholders, BA, SD, QA teams) but I've seen it utilized by other teams, like our print & warehouse departments. The whole organization has access to the tool and I believe each team does take advantage of what it offers.
I can think of a couple business problems JIRA helps solve. The most important, in my opinion, would be that JIRA provides stakeholders with a consistent avenue to request work. It clears up any confusion as to who owns such work and defines what stage the work is currently at (e.g. UAT). Another problem we've been able to rectify by using JIRA would be the issue we've had with ticket prioritization. Using boards, we can rank tickets quickly and painlessly.
I can think of a couple business problems JIRA helps solve. The most important, in my opinion, would be that JIRA provides stakeholders with a consistent avenue to request work. It clears up any confusion as to who owns such work and defines what stage the work is currently at (e.g. UAT). Another problem we've been able to rectify by using JIRA would be the issue we've had with ticket prioritization. Using boards, we can rank tickets quickly and painlessly.
- JIRA does a great job of providing flexibility for the ticket types. It can be used for a large software development project with tons of scope and it can be used for a small print job.
- Ticket management using boards is super effective and makes tracking work very simple.
- Moving tickets across different stages on a board can be a little cumbersome as tickets can sometimes not update properly and require intervention on the ticket itself.
- I'd like to see more creative widgets for the dashboard. Don't have any specific ideas but more options around metrics would be awesome.
January 25, 2015
A must have tool for an excellent software!
Score 10 out of 10
Vetted Review
Verified User
Atalassian JIRA is used in my organization in almost all phases of software development, right from the requirement analysis to deployment. Any requirement, enhancement is logged into JIRA and assigned to a requirement analyst, then it is assigned to a developer, next to QA Testing team. Each bug/defect is also logged using JIRA. It is also used for deployment where in a Sytem Engineering ticket is raised for QA, UAT, Prod deployment which is follows various approval cycles before it is deployed.
So to summarize, JIRA is used by Analyst, Developer, QA, Release Engineer, Support team, Manager, and each person who is responsible for quality and valued Software.
So to summarize, JIRA is used by Analyst, Developer, QA, Release Engineer, Support team, Manager, and each person who is responsible for quality and valued Software.
- First of all, it keeps a log of each and everything you do for a software, and it takes the responsibility of creating a process for an organization.
- It keeps track of all the bugs, completed, pending which gives a proper estimate of allocated Vs completed work and helps you to focus on the required area.
- Since JIRA has a feature to log a bug with a proper workaround, It helps a new member to go though all the open bugs in the system and find out what workaround to be applied if similar problem occurs.
- It is just perfect, no more comments!! :)
January 25, 2015
Best Defect Tracking Tool
Score 8 out of 10
Vetted Review
Verified User
Atlassian JIRA is used across all teams(Development/Business Users) across organization. It is used for Tracking defects, creating projects and listing CR's, Tasks. It provides a variety of features like creating projects, dashboards, interface with fisheye, gitcodebase etc. So every small detail and its history can be tracked within JIRA. The new JIRA version has a beautiful user interface and easy to use. My team also uses it to link JIRA with HP Quality Center which is a great addition.
- Atlassian JIRA is used to track defects/CR's etc. Details about the defect raised by a QA, then its review by business users to give a go ahead to fix the bug, Developer to analysis and fixing the bug with comments, deploying to QA for testing, Tester testing the defect and then into UAT for business user testing for its deployment to Production
- Integration with Fisheye, Stash, GIT, HP Quality Center etc
- JIRA's project Dashboard for tracking all the stories/defects.
- The new version of JIRA is a bit slow and not responsive.
- A lot of functionality added has lead to slowness in the tool
- A click here and there leads to opening a small window for adding comments which can be irritating sometimes.
December 18, 2014
Jira : Easy Project Management
Score 7 out of 10
Vetted Review
Verified User
JIRA is used to track our issues, stories and epics. It's used through the whole organization to have a view on different projects. It's also used to track time of employees that is put on tasks to be done. Without JIRA, we would not be able to easily track issues on our products.
- Can track issues on a product. It does it well and easily.
- Can monitor progress in a user story.
- Provide useful dashboard for current sprint.
- Search for issues can be very long.
- Views are not always perfect.
- Burndown and such charts can be slow to render.
December 18, 2014
JIRA review
It is used across the organization for tracking new development items and items that are identified as future scope of changes.
It helps the larger teams stay on the same page with progress of the user stories clearly
It helps the larger teams stay on the same page with progress of the user stories clearly
- Allows the owner provide estimate of time that will be required to complete a task and then compare logged time against estimated time
- Tracks end to end progress on changes being implemented
- JIRA keeps going down and becomes unavailable so often, almost stalling work progress for everyone on the team.
December 18, 2014
A skeptical JIRA user won over
JIRA was our ticketing system and Project Management tracking tool. We used JIRA both for incident management and enhancement/deployment tracking. We also used JIRA to pull statistics to determine how quickly dev teams were turning requests around and how quickly support teams were reacting to cases, updating them, and ultimately resolving them. I mostly used JIRA's reporting features to determine where bottlenecks were in our reporting and development structures.
- JIRA is extremely customizable, especially when compared to Atlassian's other flagship product, Confluence. We were able to tailor a JIRA process flow for every development and support flow that we had, even before JIRA.
- JIRA reports well. While we did find some holes in what we were able to report on, 90% of what we needed was there and readily accessible once a user was familiar with the reporting structure.
- JIRA interacts fairly well with other products. We were able to integrate it into Confluence (as it should be), but we were also able to build plug-ins into Outlook, Excel, and our phone system for more advanced functionality.
- JIRA is far too cumbersome. The learning curve to become proficient was sharp enough to cause several of our less technical people to give up learning how to truly utilize the tool, and keep things very basic. It ended up being handed over to Engineering (me, in particular because of my success with Confluence), and I also found it cumbersome but not really difficult to learn.
- While not an issue for us, I can see potential for a business to need to tailor their process around JIRA and how JIRA perceives typical ticketing/PM process.
- There are quirks with how JIRA chooses to think of business process that make the creation of some work flows more difficult and the path to engineer them less than intuitive.
December 13, 2014
My 2 cents on Atlassian Jira
Score 8 out of 10
Vetted Review
Verified User
We use JIRA to report and track issues in our organization. This includes any new feature, enhancement and bugs. This is very useful in our software development lifecycle including project initiation, requirements, development, testing and implementation. This is used in our Design and Engineering unit that is responsible for the IT development. It addresses proper logging, tracking, grouping of all the issues and their proper cost/time billing per project.
- Logging and tracking of all the issues. Its very good for Agile or Waterfall development model. You can enter all important details, group it and track all the phases.
- Great dashboard for efficient tracking and status reporting. It has visual representation to monitor the issues based on the status, criticality, phase, assignee, reporter, etc.
- For any JIRA issue, the comment section and Watchers are very helpful. People can comment on the issue many times. You can refer to any person and send automated email notification with the comments. Also you can follow any JIRA issue as watchers. Once you are a watcher, you will get automated email notification whenever any activity is done on that JIRA.
- The Upload attachment allows us to add requirements, design documents or snapshots. But there is no way you can search or find based on the attachments. Once the JIRA issues are implemented, its very hard to go to each and every JIRA and search for the requirement and design documents. If there is any way, JIRA will have option to show the JIRA number and corresponding attachment when searching through filters, that will help.
- Right now, there is no way to create a pdf out of the dashboard. If this is possible, it will help us to send the dashboard in email as a status report and people can view it without logging to JIRA.
October 06, 2014
Atlassian JIRA
Score 9 out of 10
Vetted Review
Verified User
Atlassian JIRA is used by some sections within the organisation. It is mainly used by IT for managing project work and workloads. It is also used to keep track of feature requests for a piece of software we have had externally developed for us. We are currently piloting the use of Service Desk for one of our business units.
- Easy to use and configure.
- Provides visibility of workloads.
- Provides visibility and tracking of progress against certain tasks.
- Allows you to go back and track historical decisions.
- Good roadmap, existing and new features always being worked on.
- Within the Agile area it would be nice to be able to track versions more easily, whilst it does it I don't find this area all that intuitive.
October 02, 2014
Roll up your sleeves and get started!
Score 9 out of 10
Vetted Review
Verified User
We use JIRA for engineering issue tracking for all our products. From a product management perspective it is the place I always go to find the outstanding issues and to log any issues that I might identify or that our customers may identify. We use it not only for bug tracking but also enhancement requests, escalations and various tasks. Everyone in our organizations knows the brand JIRA for engineering issue tracking, we haven't tried to conceal the underlying technology by giving it some internal system name.
- It's a great way to segment projects
- It's a great way to track issues by project
- It's a great way to capture all the critical attributes of a request being made of engineering
- The 10mb attachment limitation is sometimes annoying especially if you attach video
- It would be cool if there was tight(er) and easy (easier) integration with things like Zendesk, SharePoint and Yammer, I am not sure that we have actually invested the effort to do this integration but i am sure if it was easy as flipping a switch it would have been done.
- Sometimes the application misbehaves, I can't tell if this is infrastructure or what, usually this occurs when I am in a browser other than Chrome
- I am not aware of a mobile app for it but if there is one that would be cool
August 19, 2014
QA Manager's dream come true
We use JIRA as a task and defect tracking system across several products and divisions within our organisation. Prior to adopting JIRA several defect tracking systems were used, both internally and externally sourced solutions and so a project was started to centralise on a single system to ensure continuity between teams for reporting and implementing enterprise wide process flows.
- Integration to a wiki (Confluence) which is a must have for software development, not only the what (JIRA ticket) but the WHY (confluence page with diagrams and commentary/dialogue between contributers). You can create JIRA tickets from within Confluence and you can link to related confluence pages within JIRA.
- Several product teams follow Agile methodologies such as Scrum. JIRA comes with great support for scrum out of the box with planning boards and story point features.
- Half of the battle when using defect systems and content management is finding related issues or pulling reports from them. JIRA provides a nice syntax language for doing complex queries (JQL), the search engine is robust and it's really easy to create links between stories and the bugs found during testing.
- Dashboards are great but if you want to do more complicated queries than just showing number of open defects or bugs per week/release then the standard offerings can be limiting and often searching for solutions you are pointed towards 3rd party add-ons that are expensive.
- Time tracking is simple in JIRA but whilst there are third party time tracking/reporting tools available, it really should be something that is included in the standard product instead of a third party add-on.
- Often with stories/epics you may have started life in a Confluence page and the content is relevant, it would be nice if you could embed content from Confluence into the body of a JIRA ticket instead of just linking to the page - often you end up copy pasting paragraphs from one system to the other to communicate the point to engineers.
We use JIRA for several applications including software development project coordination, bug tracking, purchase request management, and HelpDesk ticketing.
- JIRA is an extremely flexible and feature rich issue tracking software package.
- The ability to extend the feature set through plugins and custom code as well as the comprehensive workflow settings make JIRA a great choice for any task tracking application.
- Easy integration with other Atlassian products as well as third party version control and authentication systems.
- I would like to see more fine grained control over event notifications.
August 18, 2014
JIRA - Agile Management Tool
Working in Agile methodology. As a QA team member and as a Certified Scrum Master, JIRA is very useful tool. I highly recommend to use JIRA to any individual or any organization.
- Easy to create user stories
- Easy to create and share dashboards
- Best defect tracking tool as well
- Easy and fast to install and configure
- Completely browser-based
- Training of users within no time
- Practically self-explanatory
- Scalable to all needs, no limits to users and/or projects
- Permission-based, issues can be assigned to project members
- Good and actually working workflow engine
- Usable for persons with limited technical knowledge
- Reporting should be more detailed
August 16, 2014
JIRA is a Fine Piece of Work!
I've used JIRA in my previous role at a different company that I left a couple months ago. I plan to implement it in my new role and company. JIRA has been a game changer for me both personally and professionally. I am way more organized for tasks and projects then ever before. The use of the JIRA Plug-in which allows me to use Kanban has been very helpful. I would recommend the product to anyone who loves to keep projects moving along and organized.
- Electronic Kanban board is helpful for project management and software development.
- Easy to install and learn.
- The cost is minimal compared to MS Sharepoint.
- The menu structure could take some getting use to. I still find myself searching for different areas under the menu options.