Creating New Tickets

  1. Click on New Ticket in the menu bar (you'll need to be logged in)
  2. Enter a summary for the bug/enhancement request/task that explains the problem with as few words as you need to be clear.
  3. Add a longer description for the bug/enhancement request/task that gives as many details as you think might be needed for somebody else to understand the ticket.
  4. If you want to work on the ticket immediately, assign it to yourself. Otherwise, assign it to "anybody".
  5. Set the type of the ticket to defect for bugs, enhancement for new functionality, or task for something that isn't a code change (prototyping, research, planning, changelog updating, release creation, etc...)
  6. If there is a milestone associated with the change, set it.
  7. Set the component and version to the skin the change is for and the version of the skin the problem was noticed in (or the most recent version for enhancement requests). If the skin doesn't have any versions yet, select "unversioned".
  8. Keywords, CC, and Priority can all be left alone. You're free to adjust the priority if you would like, however.

Resolving Tickets

  1. If you see a ticket that you think you should resolve, you'll want to assign it to yourself first. Do not assign a ticket to yourself that another modder has accepted without first talking to that modders. Make sure you pay attention to what skin the ticket is for.
  2. When you are ready to work on a ticket that is assigned to you, you should accept the ticket so that other modders can know you've started working on a fix (so that other modders know you're working on it, so they'll know not to take it for themselves).
  3. Once you've finished work on a ticket, and checked the code into the SVN repository, mark the ticket as "Resolved: Fixed". You will not be able to do this unless you have accepted the ticket.
    1. Sometimes, you'll determine that a ticket cannot be resolved without work from EA. In these situations, mark the ticket as "Resolved: EA Attention Required".
  4. If a ticket describes a bug or enhancement that should go into more than one skin, create a new ticket for each skin that this change should go into. Usually, you'll want to fix the same bug or add the same enhancement to every skin it belongs in at the same time, and this might make it seem like you're just wasting time creating tickets... but when each skin gets it's own ticket, it ensures that each skin gets the fix verified and makes it easier to write up changelists for individual skins.
  5. You should never verify a ticket that you resolved yourself. This ensures that any changes get tested on at least two computers, so that it is less likely for any obscure bugs to make it into releases.
    1. If you mark bugs as "Resolved: EA Attention Required", or as duplicates or invalid, you can mark them as verified yourself (there isn't a change for somebody to test, so there's no obscure bug that might've been introduced).

Verifying Tickets

See Ticketing System (for Testers).