vasanth

• Jun 15th, 2006

 

I think

Develeoper,tester,test lead

harini

• Jun 19th, 2006

 

As soon as Tester finds a bug he log that bug as NEW status and assign to Developer.When developer working on that he change the status as OPEN.When developer feels it not required to fix at that moment he changes the status as DIFFERED.If he complete working on that he change the satus as CLOSE it as FIXa nd assign to TesterTester retest the bug and change the status as closeWe have many more status as DUPLICATE, NOT REPRODUCIBLE, TO BE FIX, CRITICAL, BLOCKED, NEED CLARIFICATION.we uses the status according to the bug i hope i cleared u'r questionso DEVELOPER changes the status of the bug as DIFFERCheers,Harini.

sahana

• Jun 21st, 2006

 

When I see a defect in the application in the testing process I go to the Defects

Tab and click on Add Defect button and enter the details of the defect and attach

any snapshots of the defect and close it. The status ?New? will be assigned to

that defect. I can mail that defect to the concerned developer from TestDirector

or ask the developer to take a look at the defect in TestDirector. Developer after

seeing the defect can change the status to ?Open? which means he/she is

working on fixing it. When the fixing is done, the developer can change the status

to ?Fixed?. When developer feels it not required to fix at that moment he changes the status as DIFFERED. I can then retest the defect after the fresh build of the application and if found satisfied I can ?Close? the defect or ?Reopen? it if I am not satisfied or the defect is not fixed.

The developer has the right to ?Reject? the defect with proper reason attached to

it if he/she thinks that it is not a defect.

Archana Apte

• Jun 22nd, 2006

 

Hi

Its a big misconception that Developer will change the status of bug. Only Project Manager will decide which bug has to be given 'Deffered' satus and should be fixed later on if required.

Selvamohan Chinnasamy

• Jun 22nd, 2006

 

1.      When a Tester posts a Bug for a particular functionality, and if the developer and the Development team finds that this not of a high severity and high priority for the current build, then the person to whom the bug was assigned can defer the bug.

2.      The second scenario is that any new bug that?s been found during Ad hoc testing phase, and been escalated the development team; the team after discussion with business team can defer a bug.

Regards,

Selvamohan Chinnasamy, +9198832478

 

Antara

• Jun 22nd, 2006

 

Developer or the release management team depending on the criticality of the bug.

anand varma

• Jun 27th, 2006

 

Actually after competion all testcases execution tester reports the defect report format to developer. After taking defect format from tester developer did't got why defect was fixed then he put it into dereffered (he nither accept nor reject). He needs strong reson from tester why it made as defect. 

Ram

• Jul 4th, 2006

 

A reviewer will be there, he may be testing team lead or development team lead. In most of the cases he is development lead only.

AK

• Jul 11th, 2006

 

 

Anybody (could be the Developer, Dev' Lead, Reviewer, Release Engineer, Test Lead or Test Engineer)will have a right to change the state, when it comes to them, n it depends on various factors in different situations.

srinivasulu basetty

• Jul 12th, 2006

 

The status depends upon the priority of the bug, and the changed person is project manager or Test Lead.

kgopalakrishnamraju

• Aug 23rd, 2006

 

the status of the bug will be changed in the mrrb meeting or the minitues of meeting.this meeting will be  conducted by the QA team for discussion for the priority of the bug

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Nov 10th, 2006

 

Hi

In our Project the developer will change to Differed.. If tester logged the bug, then the developer thinks that it's no need to fixed now (as the existing functionality will not effected due this) then he change to deferred..  he can fix it in future..

Srinivasulu.B (srinivasulub1981@gmail.com)

Sridhar

• Nov 28th, 2006

 

Developer will change the status of defect as " Deffered " when assign defect (from Tester) is not a valid one .

jainbrijesh

 Profile Answers by jainbrijesh Questions by jainbrijesh

• Dec 30th, 2006

 

Different people have the right for changing the status.For ex..Developer can change status from open to fixed.CCB can change status from open to deferred or rejected etc.

dineshchandran2

 Profile Answers by dineshchandran2 

• Jul 3rd, 2008

 

When a ne bug is filed when approaching the product release, developer marks the bug as "defered" meaning the fix for this bug is postponed to next release cycle.

Regards!
Dinesh

abusaud

 Profile Answers by abusaud 

• Jul 4th, 2008

 

Bug status can be fixed by testing team lead or development team lead

vk1978

 Profile Answers by vk1978 Questions by vk1978

• Apr 9th, 2009

 

Whenever tester find a defect that is linked with the functionality or module that is not yet developed, so right now developer can't fix that defect, so developer changes the status to Deferred (meaning this bug will be fixed in coming builds)

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Sep 30th, 2010

 

It depends up on the Bug. Those who responsible for the bug will change the status as "Deferred" (who had to decide when to test it again). Most probably Project Manager..

example: If the Bug is up on configuration, then configuration manager has the right to change the defect status as "deferred". but he/she should response for when to test again(which release)

pandit

 Profile Answers by pandit 

• Dec 14th, 2010

 

Development Team & Delivery Manager  will decided to change the Status in deferred.
( If I am wrong pls inform me.)