Guidelines for adding an enhancement or feature request

Guidelines for bugs

We migrated from a Bugzilla instance. For those bugs that were migrated, a number of fields had to be mapped. These are explained below.

1. Bug number: Bug number will be auto-generated in issuetracker; the Bugzilla bug number is copied into the description field (below)

1. Component: These should map into Issuetracker’s “Subcomponent” field
   • Specific functional areas: e.g. Fees, Permissions, Groups, Clients, etc.
2. Version: Set to 1.0
3. Platform – Same as bugzilla
   • What platform are you running that generated the error.
4. OS – Same as bugzilla
   • What OS on your platform are you running when the error was generated.
5. Priority – Same as bugzilla
   • P1 being the highest priority and basically the system cannot be used with a P1 error; P2 are errors that must be fixed before the system can be used in production, and so on.
6. Issue Type – Mapped as follows:
   • Requirement: Feature
   • Design: Defect
   • Code: Defect
   • Plan: Task
   • Suggestion: Enhancement
   • Test Plan: Task
   • Test Case: Task
   • Test Stub: Task
   • Acceptance Criteria: Task
7. Assigned To – java.net username. (Assign all bugs to Swati? or Emily?)
8. Cc – Same as bugzilla
9. URL – Same as bugzilla
10. Summary – Same as bugzilla
11. Description – Same as bugzilla At the end of the bug description, add the following information from Bugzilla:
    • Original bug number from bugzilla
    • Defect Class
    • Browser
    • Test Case ID
    • How Found
    • Reporter (i.e., during migration, who originally opened the bug at Aditi) – should be both an email address and a java username.
    • Assigned To chain, if appropriate (and if not otherwise visible from the description.)
12. Ignore the following: Web Site, Projects.

1. Open the bug in java.net (If you have attachments, links to other bugs, or QA contact already). This will bring you to a new screen where you can fix the following.
   1. Attachments – Once the bug is finished, save it and then re-open the bug; this allows the attachments to be added.
   2. Bug Links – if the original bugzilla bug had links to other bugs, then those bugs should also have been migrated, and linked in this this screen.

Issue Tracker Intro

--++ Guidelines for bugs We migrated from a Bugzilla instance

Mapping from Bugzilla -

1. Bug number: Bug number will be auto-generated in issuetracker; we will copy the bug number into the description field (below)
2. Product: Component will be set to “mifos” automatically in issuetracker
3. Component: These should map into Issuetracker’s “Subcomponent” field (as of a few weeks ago, I had aligned these two)
4. Version: Set to 1.0 (only version supported in Bugzilla)
5. Platform – copy from bugzilla
6. OS – copy from bugzilla
7. Priority – copy from bugzilla
8. Issue Type – Map as follows:
   1. Requirement: Feature
   2. Design: Defect
   3. Code: Defect
   4. Plan: Task
   5. Suggestion: Enhancement
   6. Test Plan: Task
   7. Test Case: Task
   8. Test Stub: Task
   9. Acceptance Criteria: Task
9. Assigned To – if we have the java.net username of the assignee, set it to that person’s java.net username. Else, assign it to Manesh for reassignment.
10. Cc – copy from bugzilla
11. URL – copy from bugzilla
12. Summary – copy from bugzilla
13. Description – Copy from bugzilla. At the end of the bug description, add the following information from Bugzilla:
14. Original bug number from bugzilla (+ link?)
15. Defect Class
16. Browser
17. Test Case ID
18. How Found
19. Reporter (i.e., who originally opened the bug at Aditi) – should be both an email address and a java username.
20. Assigned To chain, if appropriate (and if not otherwise visible from the description.)
21. Web Site – Ignore
22. Projects – Ignore
23. Close (save) the bug in java.net
24. Open the bug in java.net. This will bring you to a new screen where you can fix the following.
25. Attachments – Once the bug is finished, save it and then re-open the bug; you will be able to add the attachment from bugzilla from this screen.
26. Bug Links – if the original bugzilla bug has links to other bugs, then migrate those bugs as well, and then fix up the links from this java.net screen.
27. QA Contact – set to the java.net ID corresponding to the aditi QA contact for the original bug.

Example of a feature:

 
Issue #: 1   Platform: All   Reporter: emilytucker (emilytucker) 
Component: mifos   OS: All     
Subcomponent: Accounting & Cash Management  
 Version: Release 0.1   CC: None defined  

Status: STARTED   Priority: P1   
Resolution:    Issue type: FEATURE   
   Target milestone: Iteration 2   
Assigned to: emilytucker (emilytucker)  
QA Contact: emilytucker 
URL:  *Use link to thread in conversation if possible* 

* Summary: Currency & Rounding Support 
  Status whiteboard:  
  Keywords:  
Attachments:    *Attach writeup here* 
  Issue 1 depends on:   Show dependency tree 
  Issue 1 blocks:   
Votes for issue 1:     Vote for this issue 

-- Main.jdailey - 25 Apr 2006