Job Log
Track and manage all customer board issues in one place.
Total
0
Open
0
In Progress
0
Resolved
0
| ID | Board Description | Customer | Type of Issue | Severity | Status | Assignee | Date | Actions |
|---|
No jobs logged yet
Add your first customer board issue using the button above.
Overview
Product summary, goals, and key context.
Product Type
Internal B2B Web App
Platform
Browser (Desktop-first)
Primary Users
Support & Engineering
Status
Draft
Product Name
Board Issue Tracker
Purpose
Log, track, and manage issues reported against customer boards — giving internal
teams a single place to capture, triage, and resolve hardware or software faults.
Access
Browser-based, internal network / authenticated users only
Core View
A sortable, filterable columned issue list — the primary working surface for all
users
Key Outcome
Reduce issue resolution time and give team leads full visibility across open
customer board faults
Issue List Columns
User Roles
Four roles with distinct permission levels and responsibilities.
| Role | Permissions | Key Actions |
|---|---|---|
| Support Agent | Create, view & update own issues | Log issues, add notes, upload evidence |
| Team Lead | View all, reassign, close issues | Triage queue, manage assignments, export reports |
| Admin | Full system access | Manage users, configure categories, board registry |
| Read-Only Viewer | View only | Monitor dashboards, generate reports |
Core Features
Click items to mark them as scoped.
0 of 17 features scoped
Issue Logging
✓
Create
new issue with customer board IDMust Have
✓
Assign
issue category (hardware, firmware, connectivity, etc.)Must Have
✓
Set
severity level (Critical / High / Medium / Low)Must
Have
✓
Attach
supporting files (images, logs)Should Have
✓
Link
related issues togetherCould Have
Columned Issue List View
✓
Sortable
columns: ID, Date, Board ID, Customer, Category, Severity, Status, AssigneeMust Have
✓
Filter
bar by status, severity, category, and date rangeMust
Have
✓
Inline
status update from list viewShould Have
✓
Column
visibility toggle (show/hide columns)Should
Have
✓
Bulk
actions: reassign, close, export selected issuesCould Have
Issue Detail View
✓
Full
issue history and activity timelineMust Have
✓
Comment
thread with @mentionsShould Have
✓
Status
transitions with required confirmation fieldsMust
Have
✓
Linked
customer and board metadata side panelShould
Have
Notifications & Reporting
✓
Email
notifications on status changeShould Have
✓
Export
issue list to CSV or PDFShould Have
✓
Summary
dashboard: open, in-progress, and resolved countsCould Have
Data Model
Fields stored per issue record in the database.
| Field | Type | Required | Notes |
|---|---|---|---|
| issue_id | UUID | ● | Auto-generated on creation |
| board_id | String | ● | Customer board identifier |
| customer_name | String | ● | Linked from customer registry |
| category | Enum | ● | Hardware / Firmware / Connectivity / Software / Other |
| severity | Enum | ● | Critical / High / Medium / Low |
| status | Enum | ● | Open / In Progress / Pending / Resolved / Closed |
| title | String | ● | Short issue summary (max 160 chars) |
| description | Text | ● | Full issue description |
| assignee | User ref | — | Internal staff member |
| attachments | File[] | — | Images, logs, supporting docs |
| created_at | Timestamp | ● | Auto-set on creation |
| updated_at | Timestamp | ● | Auto-updated on any change |
| resolved_at | Timestamp | — | Set when status changes to Resolved |
Tech Stack Recommendations
Suggested technologies — confirm with your engineering team.
These are recommendations for a typical
internal tool. Validate with your team before build begins.
Frontend
React — component-based architecture suits the list/detail view pattern well
Backend
REST API or GraphQL — Node.js or Python FastAPI are both strong choices
Database
PostgreSQL — relational model suits board / customer / issue relationships
cleanly
Authentication
SSO / OAuth 2.0 — connect to your internal identity provider (e.g. Azure AD,
Okta)
File Storage
S3-compatible object store for issue attachments
Hosting
Internal server or private cloud environment (AWS / Azure / GCP)
Audit Logging
All state changes must be logged with user ID and timestamp
Open Questions
These need answers before finalising the spec and starting build.
Q01
How many boards and customers are in scope at launch?
Q02
Is there an existing customer database to integrate with, or will boards be
entered manually?
Q03
What issue categories are needed — and can admins configure them, or is a fixed
list acceptable?
Q04
Are there SLA targets per severity level to track against?
Q05
Is offline access or mobile use required?
Q06
What does "resolved" mean — who has sign-off authority to close an issue?
Q07
Are there compliance or data retention requirements for issue logs?
User Management
Create and manage user accounts. Admin only.
Only admins can access this section. New
users can sign in immediately after creation.
Add New User
Current Users
| Name | Role | Actions |
|---|