For basic understanding: We use tickets for bug documentation, not for work coordination! If someone assigns a ticket to you, read it and fix it or reassign it to nobody if you don't want to fix it.
We have three trackers at SourceForge:
- Bug tracker for bugs in Saros
- Feature tracker for feature request
- Documentation issue tracker for documentation improvements
We use seven statuses in our ticket trackers
||The initial state. The ticket was created and has no owner
||If the ticket has an owner
||The owner accepts the ticket and will fix
||The task is done but need to be verified by someone else
||Ticket was verified and the task is done
||Defect in 3rd party software and there is no way to fix it or it's to expensive to fix it
||Use this if the reported bug isn't a bug
||Bug found in an older version or is already fixed
We use these priorities
||Has to be fixed immediately!
||Has to be fixed in the next release.
||Should be fixed in the next release. If not there should be a reason why.
||Should be fixed some day
||Not prioritized yet. Project or technical manager has to do this.