Edgewall Software

Version 8 (modified by gregmac, 10 years ago) ( diff )

add stackoverflow comment

Duplicated Check when filing new Tickets

A good example of checking new duplicates is Ubuntu LaunchPad. See also the discussions:

Another good example is http://stackoverflow.com/questions/ask. After you type in a question, the area immediately below the title (summary, in Trac) is populated with a list of questions that possibly match based on the text. This would fit into the existing Trac UI fairly easily.

Display an overview, and two links "report bug", "ask question"

bug overview

Show frequently reported bugs, and allow enter title

display most frequently reported bugs

Display possible duplicates, and allow enter bug, or notify security team

display similar tickets out of a search, and allow filing a new one


[Comments]

Duplicates are not done by LP, by HUMANS.

MostFrequentDuplicatesPlugin

Here's an idea for a plugin that could be used for doing semi-automated duplicate checking. It's pushing the idea of the MostFrequentDuplicates page a step further, by using the information collected there before new tickets get created.

We could use a bit more structure in that page, for associating patterns to tickets, e.g.

Pattern
HTMLParseError: bad end tag
Duplicate of
#4365
Note
related to a SilverCity bug
Pattern
PyGIT.py.*cannot concatenate 'str' and 'NoneType' objects
Duplicate of
#6976
Note
This is a bug in the TH:GitPlugin for Trac on nonexistent paths, see TH:ticket:2671

Before ticket creation, the ticket description should be scanned for the available (multi-line) patterns and if a match is found, a validation warning should be returned (see tags/trac-0.11/trac/ticket/api.py@#L127). This will prevent ticket creation and show a warning which can display the duplicate ticket and the associated note. See also e.g. the InterWiki module for hints about retrieving data from a Wiki page.

Attachments (3)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.