Friday, 5 August 2016

What is Web bug tracking?

The bug is an error occurred in the software development or defect occurred this bug comes while making the software if the coder makes some coding mistake then bug or defect comes in  the software.First of all, we should know about the bug tracking. It is an application that helps to keep a record of  all the bugs and defect reports in the software development. In other words, you can say keeping the records of all the errors for future reference in the project management cycle is called bug tracking. Web bug tracking is keeping the errors records online so that anyone from project management team can see that error from anywhere  24*7/ 365 days anytime. this web bug tracking is helpful when the employee is working from home or from the different city he/she can keep the records of all the bugs and can coordinate with the team working from anywhere in rectifying the bug or defect. Example like XYZ company is working in gaming software and there are 5 members in the team who is working for the same game app 3 of them is working in the office and two of them is working from home so how the employee will coordinate while  working on bugs for that web bug tracking is used.  By the help of the web bug tracking, an employee can coordinate with each other online and can resolve the error  and make a record of it for the future reference. By the help of web based tracking it helps the employee to work flexibly and can keep the record of it online so that there will be no miss communication between the employee  working from home or from the  office. A large number of bugs are called buggy.

Web bug tracking consists of the following  information:

WEB BUG TRACKING
Bug ID: Every error or defect should have a unique id number so that it can be tracked easily without miss communication .

Bug Description: you should mention the complete description of the error that what the error is all about how it appears.

Product version: Mention the version of the software in which the bug appears.so that it will be easier for the developer to rectify that.

Detail steps:  Complete information about  the bug that how it appears what is the root cause of it. So that developer can focus on that issue more.

Date raised: you should mention the date when that error occurred.

Reported by: Name of the employee who reported bug.

Status: That means whether that’s a new defect, older or its open or closed like that status should be mention correctly.

Fixed by: Name of the developer who fixed the issue and how.

Date closed:Date when the issue is resolved and report is closed

Severity: As per the severity developer can find the impact of a bug in the software.

Priority: By the priority set we can place orders  for fixing it.

A Major disadvantage for bug tracking, if it is not web based

If  bug tracking is not web based then it requires to download and installed the software on every computer in which you want to run this software. This will take more space on the computer and affect the speed of the computer and if it is properly not installed it will not work properly. Every time updating is required for the software so that meet up the current version requirement. 
But in a web tracking system do not require download and it is easy to access from anywhere, from any computer this can be used by multiple users at the same time without having the trouble of downloading  and hassle free and as it is web based it is updated automatically. 

Thursday, 4 August 2016

What is Issue Tracking Systems and its goals?


Issue tracking system is the process of generating the list of issues as needed by the company. Issue tracking system is commonly used in the call center to update the customer issue reported by them or any employee. Issue tracking plays a vital role in the customer feedback and resolving their concern on time with all legal updations regarding the same in the report. Example like XYZ company is making antivirus software and that is installed on a customer computer, but the customer still gets the virus then he/she will give the call back to that antivirus company that virus is still coming to his/her computer after installing the antivirus. Then the agent from the company ends will ask few open-ended questions than agent will check the computer and then he will open a ticket with reference number  in the customer name and he will mention all faults and errors running on his/her computer, in that ticket and at the same time he will inform the customer that we will get back to you after the work done on his/her computer. And then he will pass the ticket to the concerned department with all the details regarding errors in that this is called issue tracking system by which we can record all issues raised by the customer and pass it to the concerned department or the same person can solve and then close the ticket. In simple words you can say that issue raised by the customer or employee should be reported in the open  ticket and ticket should be close when the issue is resolved. And for that kind of report record, the application is called issue tracking system. By Issue tracking application in a call center  the employee has a great help because when the customer call in they have a small summary of customer details on the screen with all the previous notes and issue raised by the customer that helps the call center agent to understand the customer better and can make the customer happy by resolving issues and that will be more beneficial for the company because one happy customer leads  to another customer.

WORKFLOW OF ISSUE TRACKING SYSTEM

Open Ticket--------------Work in progress-----------Resolved------------Close The Ticket


Goals of issue tracking
Each goal can be taken down differently according to the project requirement and its flow of work
Capturing: In issue tracking system agent should know that what type of the issue is customer raising and where to record that issue in the application so that it reaches to the right department.issue tracking has its own temples agent just have to select the right category when recording any issue so that it reaches to the right department for its resolution.

Recording: Employee must know that where to record the issue so that it reaches to right issue resolving person.And issue resolving employee should record each bug that he captured and how customers can prevent that in future.

Accountability: By issue tracking system employee can have each record of the ticket that who has open the ticket, what is the issue recorded who is working on it and when it will be done. It helps the developer  to focus on the main error or bug recorded  by the customer end so that they can be focused more on it. It reduces miss communication gap.

Prioritization: issue tracking system helps the employee to check the things which need more attention, what can be done next it helps the employee to plan their own chart to finish the task accordingly.

Resolving: By issue tracking system, it helps the employee to record that how he/she has resolved the issue with all solution methods. So that it can further process for the closing state.
Reviewing: It helps  the employee to check whether  the issue is properly resolved or not  with the  same expectation that customers want.


For more information visit here: https://www.scopidea.com

Sunday, 21 February 2016

How to work with Bugzilla (bug tracking tool)




Let me first tell you what is a bug tracking tool??
Bug tracking tool is actually a software application that enables us to keep track of reported bugs, defects or issues. Bug tracking tool is also called defect tracking tool. There is a number of bug tracking tool available online in the market.

As we all know that Bugzilla is a bug tracking tool, which is widely used by software testers for creating reports and various other tasks. So, I think it is mandatory that every software tester should be well known to Bugzilla & its working.  Previously we discussed How to login to Bugzilla in part 1 & then we discuss that how to create reports in Bugzilla in part 2. Now today we are going to discuss that how to create graphs in Bugzilla.

Through graphs, we can view the current state of the bug database. In this, we can run reports either through HTML tables or graphical lines/pie chart. The idea behind creating graphical reports in Bugzilla (bug tracking tool) is to define a set of bugs using standard search interface & then it allows us to choose some aspect of that set to plot on horizontal as well as vertical axes. And if you choose vertical pages, then you will get a 3-dimensional plot.

Step #1:
In order to view your report in graphical representations. We first have to choose &  click on the reports from the Main Menu & after that, we have to select a graphical report from the drop down menu.

Step#2:
If for example we have to create a graph %complete vs deadline. Therefore, for this, we have to choose values on vertical as well as the horizontal axis. So, we choose %complete on vertical axis and deadline on the horizontal axis.

Now we have to set various options in order to present the reports graphically.
Ø  Vertical as well as horizontal axis
Ø  Multiple Images
Ø  Various graphs like format line graph, pie chart, bar graphs etc.
Ø  Plot data set
Ø  Classify your bug
Ø  Classify your product as well as component
Ø  Classify bug status
Ø  Select resolution
Ø  Click on generate report
After filling all these fields, we will get the required graphical report.

This is all for today’s blog on the topic Bugzilla (bug tracking tool). In our next post, we will continue our discussion and I will let know you know about Browse option, simple search option in Bugzilla and many more.

Till then please keep visiting our website www.scopidea.com for more useful & knowledgeable blogs and articles.  


Wednesday, 17 February 2016

How to work with Bugzilla (Bug Tracking Tool)



Previously we introduce our reader to Bugzilla, which is an efficient Bug Tracking Tool. You can go through that particular article by visiting Bug Tracking Tool (part 1). Today we are going to discuss how to create a bug report in Bugzilla.

Before moving further, let me tell you first what Bugzilla actually is???
Bugzilla is actually a bug tracking tool that allows one or more developers to keep track of various defects or bugs within the product.

We can create a bug report in Bugzilla bug tracking tool through following steps.
Step #1: In order to create a new bug in Bugzilla, visit the HOMEPAGE of Bugzilla & click on the NEW TAB from the MAIN MENU.

After clicking on the new bug, a new window appears with various fields in which you have to enter information regarding that particular bug.

 Step#2:  In the next window, you have to enter information in the following fields:
Ø  Enter Product
Ø  Enter Component
Ø  Give Component Description
Ø  Select Version
Ø  Select Severity
Ø  Select Hardware
Ø  Select Operating System
Ø  Enter Summary
Ø  Enter Description
Ø  Attach Attachment
Ø  Then after filling up all the above mentioned filled, just click on Submit button.
Ø  Please note that the above fields will vary as per the customization of your Bugzilla.

Here, the mandatory fields are marked with red asterisk.

Step#3:  After clicking on SUBMIT button, your bug ID is created & is assigned to your bug.  We can also add other optional information to the bug in order to give more details about the bug which we created.
Other information which we can add is:
Ø  URL
Ø  Whiteboard
Ø  Tags
Ø  Blocks
Ø  Attachments

Step#4: Within the same window, if you further scroll down. You can select a deadline date as well as the status of the bug.
From Deadline, we mean time limit which is required to resolve the bug in given time frame.

This is all for today’s blog regarding Bugzilla (Bug tracking tool). In our next article, we will discuss how to create graphical charts in Bugzilla bug tracking tool. Till then, keep visiting www.scopidea.com and enhance your technical knowledge.





Thursday, 10 December 2015

COMPARISON BETWEEN VARIOUS ISSUE TRACKING TOOLS.

What is an issue tracking system???

An issue tracking system is a software application that allows an organisation, company or institute to record and track the progress of every problem or issue by using various issue tracking tools until its status becomes fixed.

As we are provided with a number of online issue tracking tools so anyone can easily become confusing that what actually he or she should use in order to make his or her project efficient and worthy. Therefore, in order to deal with such a dilemma, we are here with a great comparison between some very exciting issue tracking tools.



We are going to compare a number of issue tracking tools  including  Bugzilla, google code hosting, HP Quality centre, Jira, mantis BT and many more. In below table we will compare different issue tracking tools on the basis its creator, implementation language, launch date, licence and features.


Now let us compare:



                                                   
        
Sr.no.

SALIENT FEATURES

LANGUAGE

LAUCH
DATE

LICENCE

CREATOR
1
Apache
bloodhound

Integrated
wiki

python

2012

apache

Apache
team












2
bugzilla

Integrated
Reports and charts

Perl

1998

MPL

Mozilla
team












3
jira

Excel,
Word and
Gantt chart

java

2002

Free licence for open source project

atlassian












4
scopidea

Ghantt chart, agile
And
Time tracking

PHP

2014

Cloud Hosted

Precise testing solution pvt ltd.












5
Planbox

RSS, charts, reporting

Java, PHP

2009

Free version

planbox















6
Support
works

Integrated,
Reporting,
dashboard

C++, java

1994

proprietary

Hornbill
systems












7
Mantis BT

Integrated
wiki

PHP

2000

Open source

GPL












8
TRAC

Integrated wiki

Python

2006

New BSD

Edgewell
software












9
WRIKE

Gantt charts, alerts, excel

java

2006

Proprietary
hosted

Wrike inc.











              
10
HP Quality centre

Reliable and
friendly

JAVA &.NET

1995

Proprietary

HP











            
11
Zoho bug
tracker

Organize
& manage
Files define custom workflows

java

2011

proprietary

Zoho corp.












12
Tracker suite.NET

Dashboard,
Graphical
report

C#

2006

proprietary

Automation
centre