Issue TrackerDocumentation
Open app
DocsOverview
ERP•AI APP PLAYBOOK

Turn pilot feedback into clear, actionable work.

Issue Tracker is the shared intake and resolution log for issues and enhancement ideas found while using the V2 timesheet pilot app. This guide explains how to submit useful evidence, manage priorities, and keep the queue trustworthy.

Start here Choose your academy
2Core tablesIssues + Users
3Operating rolesView Only, Manager, Admin
4Issue statesFrom Open to Closed
0AutomationsManual operating model
Scope note

The app currently has no workflows, custom pages, or documents. All queue movement is performed manually in the Issues table.

01 · ORIENTATION

Getting Started

Learn the workspace in five minutes, then choose the training path for your responsibilities.

1

Open Issues

Go to the Issues table. This is the operational queue.

2

Understand the record

Read Issue, Description, evidence, Type, Priority, and Status together before acting.

3

Work by role

View Only users observe, Managers triage and coordinate, and Admins steward the app and users.

4

Keep context current

Update status when work changes. Use Need more inputs when evidence is insufficient.

What a useful issue contains

  • A concise symptom or desired improvement
  • The exact dashboard or table name
  • Steps, expected result, and observed result
  • A screenshot or safe video link when helpful
  • An honest type, priority, and current status

Synthetic example

Issue
Submitted hours disappear after filter change
Dashboard/Table Name
Weekly Timesheet
Type
Bug
Priority
High
Status
Open

All examples in this guide are synthetic.

OPERATING MODEL

One visible queue, deliberate handoffs

Evidence enters once, is clarified, worked, and closed with a durable history.

Issue Tracker operating modelA four-step flow from capture to triage, resolution, and closure. CAPTUREIssue + evidence TRIAGEType + priority WORKWIP + context CLOSEOutcome verified
02 · ENABLEMENT

Role Academies

Each academy contains four practical courses. Progress is stored only in this browser and is never sent to ERP•AI or any server.

03 · STANDARD WORK

Operating Procedures

Use these procedures to keep records consistent and decisions explainable.

SOP 01Capture a new issue
  1. Search the Issues table for a matching symptom and location.
  2. Create a record only when no duplicate exists.
  3. Write one observable symptom in Issue.
  4. Name the affected surface in Dashboard/Table Name.
  5. In Description, record steps, expected behavior, observed behavior, and impact.
  6. Add safe Screenshots or a Video link if they materially clarify the report.
  7. Choose Bug or Enhancement, set a proportional priority, and begin at Open.
Data safety

Crop personal data, tokens, confidential client details, and unrelated browser content from evidence.

SOP 02Triage an issue
  1. Confirm the issue is understandable and reproducible.
  2. Use Bug for behavior that fails expectations; use Enhancement for a requested improvement.
  3. Set priority by operational impact: Low, Medium, High, or Blocker.
  4. If key context is missing, set Need more inputs and describe what is needed.
  5. If actionable work starts, set WIP.
SOP 03Update work in progress
  1. Keep the Description readable as new context arrives.
  2. Confirm attachments and links remain relevant and accessible.
  3. Reassess priority only when impact changes, not merely because time passes.
  4. Do not mark Closed until the outcome has been checked against the original report.
SOP 04Close or reopen
  1. Verify the behavior or agreed improvement.
  2. Record the outcome in Description, preserving the original context.
  3. Set Status to Closed.
  4. If the same symptom returns, set Open or WIP and add fresh evidence rather than hiding history.
SOP 05Maintain user records

Admins compare the Users table against approved access decisions, ensuring required User and Email values are present and Status reflects Pending or Active. Role and permission changes are security-sensitive and must be performed manually by an authorized person in ERP•AI.

Open Users table
04 · IN THE PRODUCT

Product Walkthroughs

5 minCore

Read the issue queue

  1. Open Issues.
  2. Scan Issue, Type, Priority, and Status.
  3. Open a record before drawing conclusions.
  4. Review Description and evidence together.
  5. Use Created At and Updated At to understand recency.
Launch Issues
8 minManager

Run a triage pass

  1. Start with Open and Need more inputs.
  2. Check location and reproduction detail.
  3. Normalize Type and Priority.
  4. Move actionable work to WIP.
  5. Leave uncertain records visible.
Read triage SOP →
6 minAdmin

Review user readiness

  1. Open Users.
  2. Check required User and Email values.
  3. Review Role and Status for anomalies.
  4. Resolve access decisions manually in ERP•AI.
  5. Return to Issues to confirm continuity.
Launch Users
ROLE FLOW

Clear boundaries, shared visibility

Roles operate on the same source of truth with different responsibilities.

Role responsibility flowView Only observes the queue, Manager triages and coordinates, and Admin stewards configuration and user records. VIEW ONLYObserveLearn patterns MANAGERTriage + prioritizeCoordinate closure ADMINStewardAudit readiness
05 · CURRENT STATE

Workflows & Automation

No workflows are configured

As of August 28, 2026, the app contains no workflow automations. There are no automatic notifications, assignments, escalations, status changes, or integrations to rely on.

What users must do manually

  • Review Open and Need more inputs regularly
  • Set Type, Priority, and Status deliberately
  • Communicate urgent Blockers through the approved team channel
  • Verify outcomes before closing records

Safe automation candidates

  • Notify a review channel when a Blocker is created
  • Remind owners about stale Need more inputs records
  • Summarize weekly status counts
  • Prompt for missing evidence before triage

These are recommendations, not current capabilities.

06 · REFERENCE

Data Model

The app contains two independent tables. No reference relationship is configured between them.

Issue Tracker data relationship diagramIssues and Users are separate tables with no configured reference field between them. System audit fields record creators and editors. ISSUESIssue · Dashboard/Table NameScreenshots · Description · Video linkType · Priority · StatusCreated/Updated audit fieldsOperational queue USERSUser · Name · First Name · Last NameEmail · Role · StatusCreated/Updated audit fieldsAccess directory NO REFERENCE
I

Issues

Operational issue and enhancement queue

Open table ↗
FieldTypeRequiredValues / purpose
IssuetextNoConcise symptom or requested improvement
Dashboard/Table NametextNoAffected product surface
ScreenshotsfileNoSupporting visual evidence
Descriptionlong_textNoSteps, expectations, observations, impact, and outcome
TypeselectNoBug Enhancement
PriorityselectNoLow Medium High Blocker
StatusselectNoOpen Closed WIP Need more inputs
Video linkurlNoSafe link to supporting video
Created At / Updated AtdateSystemRecord timestamps
Created By / Updated ByuserSystemAudit users
Sequence Format IDseq_format_idSystemGenerated sequence value
Idauto_seqSystemGenerated record identifier
DraftbooleanSystemDraft state
U

Users

App user directory and readiness state

Open table ↗
FieldTypeRequiredValues / purpose
UseruserYesERP•AI user reference
NametextNoDisplay name
First NametextNoGiven name
Last NametextNoFamily name
EmailtextYesContact email
RoleselectNoView Only Admin Manager
StatusselectNoPending Active
Created At / Updated AtdateSystemRecord timestamps
Created By / Updated ByuserSystemAudit users
07 · SUPPORT

Troubleshooting

I cannot find an issue

Clear narrow filters, search a shorter symptom phrase, and check Closed as well as active statuses. Search by the affected dashboard or table name.

I cannot edit a record

Your role may be View Only, or your user record may not be Active. Confirm your access with an authorized Admin. Do not create a duplicate as a workaround.

A screenshot will not upload

Confirm the file is local, uses a common image format, and is reasonably sized. Remove sensitive content before retrying.

A video link does not open

Check that it begins with a valid HTTPS address and that intended viewers have access. Never use a link that exposes private content publicly.

The status is unclear

Use Open for unstarted, WIP for active work, Need more inputs for blocked clarification, and Closed only after verification.

Two records describe the same issue

Keep the record with the clearest history as the working source. Cross-reference the duplicate in Description and coordinate cleanup manually.

Still blocked?

Capture the issue URL, what you expected, what happened, and a sanitized screenshot. Share that evidence through your approved support channel.

08 · DEFINITIONS

Glossary

Blocker
A priority for issues that prevent essential pilot work and have no practical workaround.
Bug
Observed behavior that does not meet the expected product behavior.
Closed
A status indicating the outcome has been verified and no further work is currently required.
Enhancement
A request to improve behavior, usability, or capability rather than correct a failure.
Evidence
Reproduction steps, screenshots, video, and contextual details that make a report understandable.
Need more inputs
A status used when progress depends on missing information or evidence.
Open
A status for a recognized issue that is not yet being actively worked.
Priority
The operational importance of an issue: Low, Medium, High, or Blocker.
Triage
The process of clarifying, classifying, prioritizing, and routing an issue.
WIP
Work in progress, the status for an issue under active investigation or resolution.
Issue Tracker Documentation

Built from the live app inventory. Examples are synthetic.

Back to top ↑Last reviewed August 28, 2026