FogBugz:How to report your issue and feedback
Nick edited this page May 16, 2011
·
1 revision
FogBugz is a project management system for Movable Type development. It helps teams work together by tracking, prioritizing, and coordinating the thousands of small tasks a development team has to do. With FogBugz, you can
- Report a bug
- Track when and how the bug is fixed
- Send a patch to fix the bug
- Submit a feature request
Everyone is welcome to join the system to contribute to the project. Please sign up to FogBugz from this page .
Please follow the steps to enter a new case for Movable Type.
- Sign in to FogBugz
- Click “New Case” in the navigation
- Enter the required fields and click “OK” to submit the case
Title | Describe your content briefly |
---|---|
Project | Select “Movable Type” |
Area | The area of your case. Please select “Feedback” if you are not sure which one to choose. |
Fix For | Select “Undecided”. Please do NOT select the other “Fix For” since the development team only check “Undecided” for the public submission cases. |
Category | “Bug” to report, or “Feature” to request. |
Assigned To | Select “Primary Contact (Bug Triage User)”. The development team only check the cases assigned to this user. |
Priority | Priority of your issue. “3 – Important” is fine for most cases. |
Version | Your Movable Type version which you see the issue. |
Textarea | Describe your issue precisely. |
Attach a file | You can attach a screen capture image or your patch code. |
- Please do NOT change any other fields.
- You can subscribe the case and receive a email notification by clicking “subscribe” button
Fogbugz’s guide provides a good instruction on writing an effective report.
You can easily insert the template formats by typing a short-code in the textarea.
- Type “bug`” to insert a bug report template
- Type “feature`” to insert a feedback template
It makes it much easier!
FogBugz provides various ways to explore the existing cases. Please refer to FogBugz’s online documentation for more detail.
Note
- Everyone can browse your cases, please do NOT write any private information in the description.
- Please do NOT change or edit “Fix For” and “Assigned To”. We may lose the case if it’s changed inappropriately.
- For each case please refer to a single bug or a feedback.
- Please make sure that the report contains enough information to reproduce your bug. Especially your server/browser environment and “steps to reproduce” are both essential.
Thank you very much for your help !