Sage_Software/2002-Chevy-Express-1500
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
main
2002-Chevy-Express-1500/ISSUE_TEMPLATE.md
T
John Loper II 0627004769 docs: Add timestamp requirement to issue template 
- Updated ISSUE_TEMPLATE.md with stricter timestamp guidelines
- Added requirement: EVERY entry must have timestamp - no exceptions
- Added examples of entries that need timestamps
- Added section on common mistakes to avoid
- Created memory note: /workspace/memory/TIMESTAMP-REQUIREMENT.md
- All future progress.md entries will follow YYYY-MM-DD HH:MM format
2026-03-22 19:49:17 -04:00

7.7 KiB
Raw Permalink Blame History

Vehicle Issue Template

Use this template for new vehicle issues. Copy to a new subfolder within your vehicle's main project folder.

🚗 Vehicle Information

Field Value
Year/Make/Model [e.g., 2002 Chevrolet Express 3500]
Engine [e.g., 5.7L V8]
VIN [Optional: for parts lookup]
Mileage [Current odometer reading]
Date Started [YYYY-MM-DD]

📋 Quick Summary

Problem: [Brief description of the issue]

Current Status: [e.g., 🔍 INVESTIGATION / 🔧 PARTS NEEDED / ✅ RESOLVED]

Urgency: [High/Medium/Low - e.g., "High - vehicle not drivable" or "Low - can wait"]

Related Issues: [Any connections to other issues, codes, or symptoms]

🔍 Symptoms

  • [Symptom 1]
  • [Symptom 2]
  • [Symptom 3]
  • [Symptom 4]

When it occurs: [e.g., "Cold start only," "At idle," "Under load," "Random"]

Frequency: [Always / Sometimes / Rarely]

📊 Diagnostic Findings

NOTE: All diagnostic steps and actions MUST include full timestamps (YYYY-MM-DD HH:MM) for tracking progress across multiple days.

Initial Inspection Results

  • [Inspection item 1 - e.g., Fluid level low] [@YYYY-MM-DD HH:MM]
  • [Inspection item 2 - e.g., No visible leaks] [@YYYY-MM-DD HH:MM]
  • [Inspection item 3 - e.g., Check pressure] [@YYYY-MM-DD HH:MM]
  • [Inspection item 4 - e.g., Test electrical] [@YYYY-MM-DD HH:MM]

Test Results

Test Expected Actual Status Tested At (YYYY-MM-DD HH:MM)
[Test 1] [Expected value] [Actual reading] ✅/❌/⚠️ [YYYY-MM-DD HH:MM]
[Test 2] [Expected value] [Actual reading] ✅/❌/⚠️ [YYYY-MM-DD HH:MM]
[Test 3] [Expected value] [Actual reading] ✅/❌/⚠️ [YYYY-MM-DD HH:MM]

Diagnostic Data Collected

  • [Test 1]: [Results and conclusions]
  • [Test 2]: [Results and conclusions]
  • [Test 3]: [Results and conclusions]

🎯 Theories & Root Cause Analysis

Most Likely Causes (ranked by probability)

  1. [Theory 1 - Most Likely]

    • Why: [Reasoning]
    • Evidence: [Supporting data]
    • How to confirm: [Next diagnostic step]

  2. [Theory 2]

    • Why: [Reasoning]
    • Evidence: [Supporting data]

  3. [Theory 3]

    • Why: [Reasoning]

Common Failure Points for This Vehicle

  1. [Common issue 1]
  2. [Common issue 2]
  3. [Common issue 3]

Historical Context

  • [Previous issues on this vehicle]
  • [Known patterns or recurring problems]
  • [Related codes or symptoms]

🛠️ Tools Needed

Basic Tools

  • [Tool 1]
  • [Tool 2]
  • [Tool 3]

Specialized Tools

  • [Tool 1]
  • [Tool 2]

Safety Equipment

  • [Safety glasses]
  • [Gloves]
  • [Jack stands]

📦 Parts & Materials

Parts Needed

Part Part Number Cost (Aftermarket) Cost (OEM) Status
[Part 1] [e.g., 88915445] $[00-00] $[00-00] 📝 Needed / 📋 Awaiting / ✅ Ordered
[Part 2] [e.g., -] $[00-00] $[00-00] 📝 Needed / 📋 Awaiting / ✅ Ordered

Materials

  • [Fluid type and quantity]
  • [Sealant type]
  • [Cleaning supplies]

Purchased Parts

  • [Part Name]: [Where purchased], [Cost], [Date]
  • [Part Name]: [Where purchased], [Cost], [Date]

📚 Resources

Video Resources

Written Guides

Parts Sourcing

  • 🔗 [RockAuto link]
  • 🔗 [eBay search link]
  • 🔗 [Local parts store with VIN lookup]

Technical References

  • [Service manual reference]
  • [Technical service bulletins]
  • [Forums or community resources]

🔧 Repair Procedure

Step-by-Step Instructions

  1. [Preparation Step]

    • [Detail]
    • [Safety note if applicable]

  2. [Removal/Disassembly Step]

    • [Detail]
    • [Torque specs if applicable]

  3. [Inspection Step]

    • [What to look for]
    • [Acceptable vs unacceptable conditions]

  4. [Replacement/Repair Step]

    • [Detail]
    • [Orientation notes]

  5. [Reassembly Step]

    • [Detail]
    • [Torque specs if applicable]

  6. [Testing Step]

    • [Verification procedure]
    • [Success criteria]

Scenario-Specific Procedures

Scenario 1: [Specific Failure Mode]

When to use: [Conditions that indicate this scenario]

  1. [Step 1]
  2. [Step 2]
  3. [Step 3]

Time: [Estimated duration] Difficulty: [Easy/Moderate/Hard]

Scenario 2: [Another Failure Mode]

When to use: [Conditions that indicate this scenario]

  1. [Step 1]
  2. [Step 2]
  3. [Step 3]

Time: [Estimated duration] Difficulty: [Easy/Moderate/Hard]

📋 Next Steps

  • [Immediate next action]
  • [Purchase parts]
  • [Schedule repair]
  • [Test after repair]
  • [Verify success]
  • [Clear codes if applicable]
  • [Test drive]

📅 Session Log

IMPORTANT: All entries MUST include full timestamps (YYYY-MM-DD HH:MM) to track issue progress across multiple days.

CRITICAL RULE: Every single entry in the session log must have a timestamp. No exceptions.

  • [YYYY-MM-DD HH:MM]: [Event description - e.g., "Project initiated, diagnosis started"]
  • [YYYY-MM-DD HH:MM]: [Event description - e.g., "Diagnostic tests completed, root cause identified"]
  • [YYYY-MM-DD HH:MM]: [Event description - e.g., "Parts ordered, awaiting delivery"]
  • [YYYY-MM-DD HH:MM]: [Event description - e.g., "Repair completed, van running fine"]

Session Log Guidelines:

  • Use full timestamp format: YYYY-MM-DD HH:MM (24-hour format)
  • Include timestamp for EVERY action, test, and decision
  • Track when parts were ordered, received, and installed (may span multiple days)
  • Note when tests were performed and results observed
  • Record when vehicle was test-driven and any issues found
  • This enables accurate troubleshooting timeline and pattern recognition across multiple days
  • Do not skip timestamps for any entries - even quick notes or observations
  • Include timestamp for EVERY action, test, and decision
  • Track when parts were ordered, received, and installed (may span multiple days)
  • Note when tests were performed and results observed
  • Record when vehicle was test-driven and any issues found
  • This enables accurate troubleshooting timeline and pattern recognition across multiple days

📝 Notes

  • [Important notes about the issue]
  • [Lessons learned]
  • [Tips for future reference]
  • [Warnings or cautions]

🔄 Related Issues

Previous Issues

  • [Link to related issue 1] - [Brief description]
  • [Link to related issue 2] - [Brief description]

Pending Maintenance

  • [Item 1] - [Urgency] - [Cost estimate]
  • [Item 2] - [Urgency] - [Cost estimate]

📊 Success Criteria

Before Starting

  • [Criteria 1]
  • [Criteria 2]

After Repair

  • [Criteria 1 - e.g., "Pressure reaches 55+ PSI on first prime"]
  • [Criteria 2 - e.g., "No check engine light"]
  • [Criteria 3 - e.g., "Smooth idle at 53-54 PSI"]
  • [Criteria 4 - e.g., "No leaks after 24 hours"]

Verification Steps

  1. [Test procedure 1]
  2. [Test procedure 2]
  3. [Test procedure 3]

🧪 Revision History

Date Change
YYYY-MM-DD Initial creation - [Brief description]
YYYY-MM-DD Updated [section] - [Brief description]
YYYY-MM-DD [Other change]

🔗 See Also

  • [Link to main vehicle project README]
  • [Link to related issue folder]
  • [Link to diagnostic notes]
Reference in New Issue View Git Blame Copy Permalink