4. DATA RESULTS From the data table (Fig 1.1) comparisons of different bug tracking tools and their features are shown. For the bug tracker or project manager’s features are very important to them. From the (Fig 1.1) it is clear that bug tracking tools are different to one another from the feature’s point of view respectively.4.1. Some bug tracking tools are paid 55 and some are open sources. It depends on the bug tracker of a company’s project manager to choose whether a paid or open sources for tracking the bugs 1-6. 4.2. Bug tester will be more willing to select a defect tracking tool which has intuitive user interface 2-8.4.3 Bug tracker’s adaptable workflow example aides should define single person workflows for distinctive ventures. In this way that it gets not difficult should design workflows on reflect at whatever organization’s interesting needs. Some of the researched bug tools have this feature 3-10.4.4 From agile boards to reports, bug tracker can plan, track, and manage all the agile software development projects from a single tool 4-14.4.5 Plug in API feature provides a very flexible framework for adding features to the tools fig 1.1 or modifying certain existing functionality, using plugins. The system has been created to utilize an event-based hook system, but also allows plugins to create new view pages and more. Most anything that isn’t directly allowed by the plugin system can easily be added on using the existing framework as a building block 5-7.4.6 Full text search feature helps the selected bug tracking tools by reported issues which are easy to find with search and filters 6-12. 4.7 When a code is changed the e-mail notification feature helps the tick marked bug tracking tools (fig 1.1) to notify the bug testers that a changes have been done 7-8.4.8 Cloning, or copying, an issue helps quickly to create a duplicate of an issue within the same project. Those clone issue will be a reproduce of the unique issue, holding those same majority ¬¬of the data saved in the unique issue — example: summary, influences versions, segments. The clone issue can also be linked to the original issue. Some bug trackers are able to handle the clone defects 9-14.4.9 In the (fig 1.1) some bug tracking tools are available in mobile applications 9-14.4.10 Various types of source code repository hosts are available, whether they are for open source projects or multi-developer projects, for single developers or private teams. These web hosting facilities often support various services and tools, including bug tracking. Some bug tracking tools have got this necessary feature 15-17.4.11 Software testing metrics are an approach to measure the different level of test activities. Necessities are it provides for knowledge under the team’s test progress, productivity, and the nature of the framework under test. At those bug testers might ask themselves that “What have they tested?” then metrics will provide for them preferred replies. Diverse group’s measure different parts relying upon the thing that they need to track what’s more control or move forward. And except BugTracker.NET others have this feature 18-20.4.12 The worth of effort of kanban groups revolves around a kanban board, an instrument used to visualize fill in and streamline those stream of the worth of effort around the group. It is a standout amongst the others mainstream software improvement methodologies embraced by agile groups today. Kanban offers a few extra points of interest to errand arranging. Kanban and scrum both of them share some of the same concepts but they use different approaches. In case of Scrum it does “regular fixed length sprints (2 weeks)” whereas “continuous flow” is done by kanban. And most of the researched bugs tracking tools (fig 1.1) have this feature 21-23.4.13 The drag-and-drop strategy inside every project permits the coordinator to assign and monitor progress 24-27.4.14 The dashboards are the first screen when a user will log in. It can be configured to display many different types of information, depending on the user areas of interest. The information boxes on the dashboard are called gadgets. User can easily customize the dashboard by choosing a different layout, adding more gadgets, dragging the gadgets into different positions, and changing the look of individual gadgets 28-30.4.15 Workflow is considered as another important feature. If one and the same issue moves from one team members to another member then a simple workflow won’t work. Moreover, if the user company is a small team, a simple workflow might be perfect. Additionally, according to many users, Jira is better than others in many respects. For example, Jira’s visual workflow designer allows designing custom workflow for any team’s unique work process. Also, in Jira, users can create custom dashboards that contain all the information require to plan and track the work. There are huge of gadgets available that can help the users during the process 31-35.4.16 From the research bug tracking tools some offers a level of streamlining, which removes the need for software dependencies and offers a more centralized location for project tracking. Having a singular point of reference for the status of a project that can be update in real time, grants clarity as to the progress of each involved team 36-37.4.17 In fig (1.1) the bug trackers those are hosted in the cloud means user don’t have to worry about buying and maintaining own infrastructure. It’s also instantly setup – so user doesn’t have to tense a techie to install and configure it, besides, there are no bandwidth limits so users can use the system as much as they like and that makes more easy and reliable 38-40.4.18 Some bug tracking tools (fig 1.1) are capable of data center deployment. The benefits of Data Center over Server deployments are environment, procedure, high availability, performance at scale, instant scalability, and disaster recovery 41-43. 4.19 Web-based Architecture feature is designed and developed to operate on the web. All the features and functionality are available to the user with a web browser. These features help the bug trackers (fig 1.1) easy to use and deploy, provide full access from any platform, anywhere and no client-side installation 44-48.4.20 Bug tracking tools (fig 1.1) provides a simple way to create screen captures and attach them to items of bug tracking or problem management system, example: in order to report a bug or to explain an improvement suggestion visually 49-54. 4.21 Agile planning and reporting is a necessary feature for the bug’s tester. Among the bug tracking tools (fig 1.1) some supports any agile project management methodology for software development. They are agile project management tools that support any agile methodology, which can be scrum, kanban, or bug tester’s unique problem. From agile boards to reports, bug testers can track, plan, and manage all agile software development projects from a single tool. Scrum is an agile methodology where products are made in a series of fixed-length iterations. There are four pillars such as: sprint planning, daily scrums, sprints, and retrospectives that bring structure to the framework 55-57.