From: Beecher, K. <Kar...@fu...> - 2011-07-12 13:56:34
|
Ideally you should always check the tracker to see if your issue already exists. If it does (and is closed), then it is really down to how the individual interprets the old entry. Generally, you should bias towards re-opening, because the old entry could have important information relevant to understanding the problem. Some guidelines I suggest: If the old entry describes the *exact* same problem you have now, then definitely re-open. If the old entry is similar and marked with a resolution suggesting no work was done ("out of date", "invalid", etc), then you should re-open. If it is similar and marked as fixed, it might be a better idea to open a new entry (and include a reference to the old one). After all, the code around the old bug changed since the old entry was added, so the problem -- while similar -- might be better described as caused by a different bug. Reopening should be available to everyone listed as a project member. > -----Original Message----- > From: Rosen, Edna [mailto:edn...@fu...] > Sent: Tuesday, July 12, 2011 2:09 PM > To: 'dpp...@li...' > Cc: 'ag...@mi...'; 'Saros Mailinglist' > Subject: [Dpp-devel] Handling of closed but unfixed duplicate bug > reports? > > Hi all, > > I would be interested in knowing what the general approach to duplicate > bug reports in case of their reoccurrence is. > Should the old bug report be reopened if closed? Is this even possible? > Or should the new bug report be marked as duplicate but kept open until > the problem is resolved if the old one is already closed? > > Ex. See: ID: 3348982 > > Edna > > > > > ----------------------------------------------------------------------- > ------- > All of the data generated in your IT infrastructure is seriously > valuable. > Why? It contains a definitive record of application performance, > security > threats, fraudulent activity, and more. Splunk takes this data and > makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Dpp-devel mailing list > Dpp...@li... > https://lists.sourceforge.net/lists/listinfo/dpp-devel |