Edgewall Software

Changes between Version 9 and Version 10 of TracDev/Proposals/NewTicketDuplicateCheck


Ignore:
Timestamp:
Apr 9, 2015, 12:13:53 PM (4 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified
  • TracDev/Proposals/NewTicketDuplicateCheck

    v9 v10  
    1 = Duplicated Check when filing new Tickets =
     1[[PageOutline(2-5,Contents,pullout)]]
    22
    3 A good example of checking new duplicates is [https://bugs.launchpad.net/ubuntu/+filebug Ubuntu LaunchPad]. See also the discussions:
     3= Duplicate check when filing new tickets
     4
     5A '''new duplicate ticket''' is a new ticket that has been posted before. For the background into the issues surrounding new duplicate tickets, see the following discussions:
    46 * [http://groups.google.com/group/trac-dev/browse_thread/thread/d07c7ed673eb170e NewTicket duplicates discussion]
    57 * [http://groups.google.com/group/trac-dev/browse_thread/thread/2db506098b5b6276 ticket duplicate discussion]
     
    79 * [http://trac-hacks.org/wiki/DuplicateTicketSearchPlugin DuplicateTicketSearchPlugin on trac-hacks]
    810
    9 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.
     11Good implementations of checking new duplicate tickets are:
     12 * [https://bugs.launchpad.net/ubuntu/+filebug Ubuntu LaunchPad]. See screenshots below.
     13 * [http://stackoverflow.com/questions/ask Stackoverflow]. 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.
    1014
    11 == Display an overview, and two links "report bug", "ask question" ==
     15== Display an overview, and two links "report bug", "ask question"
     16
    1217[[Image(01-bug-overview.png)]]
    1318
    14 == Show frequently reported bugs, and allow enter title ==
     19== Show frequently reported bugs, and allow enter title
     20
    1521[[Image(02-most-frequently-reported.png)]]
    1622
    17 == Display possible duplicates, and allow enter bug, or notify security team ==
     23== Display possible duplicates, and allow enter bug, or notify security team
     24
    1825[[Image(03-really-enter-bug.png)]]
    1926
     27== !MostFrequentDuplicatesPlugin
    2028
     29Here is an idea for a plugin that could be used for doing semi-automated duplicate checking.
     30It is a more automated version of what is described in the MostFrequentDuplicates page, by using the information collected there ''before'' new tickets get created.
    2131
    22 ----
    23  = [Comments] =
    24 Duplicates are not done by LP, by HUMANS.
    25 
    26 == !MostFrequentDuplicatesPlugin ==
    27 
    28 Here's an idea for a plugin that could be used for doing semi-automated duplicate checking.
    29 It's pushing the idea of the MostFrequentDuplicates page a step further,
    30 by using the information collected there ''before'' new tickets get created.
    31 
    32 We could use a bit more structure in that page, for associating patterns to tickets, e.g.
     32We could use a bit more structure in that page, for associating patterns to tickets. Examples:
    3333
    3434 Pattern:: HTMLParseError: bad end tag
     
    4040 Note:: This is a bug in the TH:GitPlugin for Trac on nonexistent paths, see TH:ticket:2671
    4141
    42 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 [source: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 [source:tags/trac-0.11/trac/wiki/interwiki.py InterWiki] module for hints about retrieving data from a Wiki page.
     42Before ticket creation, the ticket description is scanned for the available (multi-line) patterns and if a match is found, a validation warning should be returned (see [source: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 the [source:tags/trac-0.11/trac/wiki/interwiki.py InterWiki] module for hints about retrieving data from a Wiki page.