Analyze
FogBugz - Documention cases creation and analysis
Case creation inputs
-
Inputs for document case creation is provided by the following channels:
-
DocTeam
-
Product Owners
-
Developers
-
Internal Customers
-
DocTeam case handling scenarios
-
The DocTeam handles cases in the following scenarios:
-
DocUpdate Cases: When Product Owners or Developers mark a case with DocUpdate tag in FogBugz, the DocTeam creates a sub/child case, marking the original case as the parent. After creating the sub/child case, the DocUpdate tag is removed from the parent case.
-
DocTeam Cases: If DocTeam identifies a need for refinement in a document, the team creates a case to address the necessary corrections or improvements.
-
|
When DocTeam creates a new case in FogBugz, it is necessary that the following fields are filled as follows, i. Project → Documentation ii. Area → Select it according to a particular case iii. Category → Inquiry (Initially, the category is set as "inquiry" until the respective Product Owner or Developer approves the changes for updating. Once approved, the category will be changed accordingly) iv. Assign to → DocTeam |
Post-case creation
-
Once the case is created, inquire the case with the case creator to set priority and due date.
-
Then assign the case to the specific DocTeam member.
Document analysis
-
The assigned member has to analyze the case input.
-
Clarify any doubts with the Product Owners.
-
Ensure quality input is received within a reasonable time period.
-
If received, proceed to create a document skeleton.
-
If not received, mark the case with NeedInfo tag in FogBugz and proceed with document creation based on available knowledge.
-
Content addition/editing
-
Start adding or editing content in the document.
-
For more details on the adding/editing process, refer to Edit.
How to create case in FogBugz
-
Log in to FogBugz
-
Click on New case.
-
Enter the case Title.
-
Select Documentation from Project dropdown list.
-
Select the Area that corresponds to a particular case.
-
Select the Category that corresponds to a particular case.
Inquiry, Feature, Refinement and Bug are the categories frequently used by Documentation team. 
-
Assign the case to a person or a team by selecting the Assigned To dropdown list.
-
Set the Status of a particular case.
Active, For Review, For Merge and Ready to Ship (Publish) are the statuses frequently used by Documentation team. 
-
Add users in Notify More Users about the status of your project.
-
Set Priorities based on the task requirement.
-
Add parent cases and subcases if applicable.
-
Add due date as required.
-
Click the Open button to create a case.
| The creator of a specific case is responsible for closing it once the content for the case is published. |