Changes between Version 3 and Version 4 of MakingTickets


Ignore:
Timestamp:
Mar 28, 2013 11:10:37 AM (5 years ago)
Author:
zach
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MakingTickets

    v3 v4  
    1111 
    1212=== Search! === 
    13 Do a quick [/project/search search] before filing your ticket. While Colloquy doesn't get full updates on a regular basis, bugs are constantly being fixed. This means there's a chance your problem might have been fixed already! If the problem has been solved, you can build Colloquy's [wiki:"Source Code" source code] and have the latest changes.  
     13Do a quick [/search search] before filing your ticket. While Colloquy doesn't get full updates on a regular basis, bugs are constantly being fixed. This means there's a chance your problem might have been fixed already! If the problem has been solved, you can build Colloquy's [wiki:"Source Code" source code] and have the latest changes.  
    1414 
    1515Be sure to keep an eye out for tickets similar to yours. If you want to be really helpful, jot down the numbers and mention them at the end along with the ticket summary. 
    1616 
    1717=== Do I have to sign up file a ticket? === 
    18 You don't have to sign up to file a bug report or an enhancement request for Colloquy. However, if you want to make a followup comment or attach additional files, you will need to [/project/register register] and [/project/login log in].  
     18You don't have to sign up to file a bug report or an enhancement request for Colloquy. However, if you want to make a followup comment or attach additional files, you will need to [/register register] and [/login log in].  
    1919 
    2020=== Any questions? === 
     
    2424 
    2525=== Make a short summary === 
    26 When looking over [/project/report/1 open trac tickets], we only see a short summary of the problem. The more concise and well written the summary is, the quicker we can see what the ticket is about when looking through the list. 
     26When looking over [/report/1 open trac tickets], we only see a short summary of the problem. The more concise and well written the summary is, the quicker we can see what the ticket is about when looking through the list. 
    2727 
    2828=== The Problem (Alternately, The Request) ===