-
In my experience, almost all metadata fields are used rigorously. The process is documented in detail.
-
Related to the ticket flags, I wrote some code that adds a yellow box underneath the description of each open ticket “According to the ticket’s flags, the next step(s) to move this issue forward are:” to help guide newcomers regarding the triage process:
-
To go along with community triage, as far as I know, it’s impossible to assign a GitHub issue to someone not a member of the repo’s organization.
-
Trac supplies data to https://dashboard.djangoproject.com/.
-
I highly value searching the tracker using Google’s site:code.djangoproject.com filter.
-
When committing a patch, a comment is automatically added to the ticket which makes it easy to see its resolution, as well as if the patch was backported to another branch.
-
The GitHub issue tracker adds a comment to an issue every time a commit with the issue number is pushed with the ticket number which makes things quite ugly when force-pushing to amend a PR. Example:
