Creating Tickets
A ticket in Elgg Trac can be one of defect, enhancement, patch or feature request. Make sure you document your ticket well, because this is where all discussion will get tracked and developers will want to know all details. If you've found a bug, try to make a patch, developers love patches. See SubmittingPatches for more details.
Some guidelines before submitting a ticket:
- make sure you have searched the existing tickets to see if your issue hasn't been reported yet,
- also make sure you have searched the Elgg Google Group for similar issues,
- try a nightly build, it may very well be your issue has already been resolved,
- else, please write complete, reproducible, specific bug reports. Include as much information as you possibly can, including error messages, snippets of code or whatever you think might be necessary.
- remember that tickets aren't supposed to be used for support requests, use the main site forum for this.
When creating a ticket you'll also see there is an option to set a milestone. A milestone is part of a roadmap, and it will ultimately be the core developer group that will assign your ticket to a milestone.
Developers will most likely focus on milestone information to determine if a ticket has been triaged or not. Ticket triage is an area where you can contribute too, see TicketTriage for more information.
Once your ticket has been accepted and linked to a milestone, development will continue and the ticket will get closed once all is done.
Big ideas
You love Elgg, but think it is missing something and your idea doesn't fit a ticket? Use the Elgg Google Group to explain why you think your idea rocks and why it should get put on the roadmap. Once your idea has reached consensus, you can start thinking again about adding tickets in Elgg Trac for it to happen.
