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

Timestamp:

Mar 6, 2023, 11:41:30 AM (14 months ago)

Author:

figaro

Comment:

Cosmetic changes

TracDev/Proposals/NewTicketDuplicateCheck

@@ -6 +6 @@
  * [http://groups.google.com/group/trac-dev/browse_thread/thread/d07c7ed673eb170e NewTicket duplicates discussion]
  * [http://groups.google.com/group/trac-dev/browse_thread/thread/2db506098b5b6276 ticket duplicate discussion]
- * [#MostFrequentDuplicatesPlugin] proposal
- * [http://trac-hacks.org/wiki/DuplicateTicketSearchPlugin DuplicateTicketSearchPlugin on trac-hacks]
+
+Note that a plugin exists that implements a search for possible duplicate ticket entry: [th:DuplicateTicketSearchPlugin] and partially implements the [#MostFrequentDuplicatesPlugin] proposal below.
 
 Good implementations of checking new duplicate tickets are:
@@ -15 +15 @@
 == Display an overview, and two links "report bug", "ask question"
 
-[[Image(01-bug-overview.png)]]
+[[Image(01-bug-overview.png, border=2)]]
 
 == Show frequently reported bugs, and allow enter title
 
-[[Image(02-most-frequently-reported.png)]]
+[[Image(02-most-frequently-reported.png, border=2)]]
 
 == Display possible duplicates, and allow enter bug, or notify security team
 
-[[Image(03-really-enter-bug.png)]]
+[[Image(03-really-enter-bug.png, border=2)]]
 
 == !MostFrequentDuplicatesPlugin
 
-Here is an idea for a plugin that could be used for doing semi-automated duplicate checking.
-It is a more automated version of what is described in the MostFrequentDuplicates page, by using the information collected there ''before'' new tickets get created.
+Here is an idea for a plugin that could be used for doing semi-automated duplicate checking. It is a more automated version of what is described in the MostFrequentDuplicates page, 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. Examples:
+We could use a bit more structure in that page to associate patterns to tickets. Examples:
 
  Pattern:: HTMLParseError: bad end tag
@@ -36 +35 @@
  Note:: related to a SilverCity bug
 
- Pattern:: PyGIT.py.*cannot concatenate 'str' and 'NoneType' objects
+ 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