Page History

...

1. Bug - A defect.
2. Feature - New functionality or a significant upgrade to existing functionality.
3. Tweak - A minor enhancement, re-factoring or code cleanup. Tweaks are small in scope. As a rule they should be no more than 2 weeks in duration.
4. Task - A work item that does not change the repository.  Examples: baselining the PRD, open source approvals or architecture reviews.
5. Test - A fix or update to the test suite.
6. Sub-task - A sub item of any of the above.
7. Optimization -  Deprecated - Do not use this issue type.

IMPORTANT: Many processes are different for different issue types.  Unless you are a committer, submit only Bugs.

More Detail About Issue Types

Features get tracked against as larger work items while Bugs and Tweaks do not.  Tests and Tasks may be allowed at times when Features, Tweaks or Bugs are restricted.  Bugs are counted in quality metrics while other types are not.  As a result it's important to get the issue type right.  Calling something a Bug rather than a Feature or calling any kind of code change a Task are the most common mistakes.

...

This is the most important part of the bug.  A bug that cannot be recreated cannot be fixed.  In fact, committers won't make code changes without a test case that shows the problem and then shows the that problem is gone after the fix is applied.When you submit a bug, please supply sample code that demonstrates the problem and numbered steps.

The best way to ensure that a bug can be recreated is to provide:

• a complete code sample
• a set of steps (numbered is best)

Here is an example:

//TODO - complete this very critical section with and examplefind good example in JIRA

Environment

This field is used to capture the platform where you are running.

...