CityTrack / .github /ISSUE_TEMPLATE /FEATURE_REQUEST.md
0xarchit's picture
Initial commit: CityTrack MVP with documentation, templates, and license
15cfc64
metadata
name: Feature Request
about: Suggest a new feature or improvement for CityTrack
title: '[FEATURE] '
labels: enhancement
assignees: 0xarchit

Description

Provide a clear and detailed description of the feature you'd like to see.

Problem It Solves

What problem does this feature address? Why is it needed?

  • Current workflow pain point:
  • User frustration:
  • Impact:

Proposed Solution

Describe how you envision this feature working:

  1. User would...
  2. System would...
  3. Result would be...

Alternatives Considered

Have you thought of alternative solutions or features?

  • Option A: ...
  • Option B: ...

Use Cases

Describe real-world scenarios where this feature would be useful:

Use Case 1:

  • Actor: (e.g., Citizen, Worker, Admin)
  • Action: ...
  • Expected outcome: ...

Use Case 2:

  • Actor: ...
  • Action: ...
  • Expected outcome: ...

Affected Components

Which parts of CityTrack would this feature affect?

  • Mobile App (Citizen)
  • Admin Dashboard
  • Worker Portal
  • Backend API
  • Database
  • AI/ML Pipeline

Acceptance Criteria

What would make this feature "done"?

  • Criterion 1
  • Criterion 2
  • Criterion 3

Additional Context

Add any other context, mockups, or references here.

Priority

  • Critical (Blocking other features)
  • High (High user impact)
  • Medium (Nice to have)
  • Low (Enhancement)

Related Issues

Link to any related issues: #123


Checklist:

  • I've checked if this feature already exists
  • I've searched for existing feature requests
  • I've provided clear use cases
  • The scope is well-defined