Changes between Version 3 and Version 4 of TicketWorkflow

Timestamp:

Jul 6, 2007, 2:30:42 AM (15 years ago)

Author:

Dave Abrahams

Comment:

--

TicketWorkflow

@@ -7 +7 @@
 The ticket reporter's name is a !SourceForge userid.  You can keep that person abreast of developments by adding `@users.sf.net` to the userid—then they'll get emails about all changes to the ticket.  
 
-== Move attachments over from SourceForge ==
+== Move attachments over from !SourceForge ==
 
-Unfortunately when the tickets were moved over from SourceForge, attachments were not moved with them.  You can find the old tickets [http://sourceforge.net/search/?group_id=7586&words=dave&type_of_search=artifact&pmode=0&words=&Search=Search here], download the attachments, and attach them to the Trac tickets.  Having a complete record is important to Boost's integrity!
+Unfortunately when the tickets were moved over from !SourceForge, attachments were not moved with them.  You can find the old tickets [http://sourceforge.net/search/?group_id=7586&words=dave&type_of_search=artifact&pmode=0&words=&Search=Search here], download the attachments, and attach them to the Trac tickets.  Having a complete record is important to Boost's integrity!
 
 == Fix the Bugs that are Assigned to You ==
 
 (Duh!) If you're logged in, here they are, in order of decreasing priority: report:9
-However, if your SourceForge UserID is not the same as your Trac UserID, you may have a whole slew of other open tickets.  See report:12 for all the owned tickets.
+However, if your !SourceForge UserID is not the same as your Trac UserID, you may have a whole slew of other open tickets.  See report:12 for all the owned tickets.
 
 == Triage Unassigned Tickets ==