Saltar al contenido principal

jira-like old

Purpose and Production Relevance​

jira-like old is an older copy of the jira-like planning app. Treat it as legacy unless a migration or comparison task explicitly requires it.

Production relevance: legacy copy.

Stack and Main Dependencies​

The nested app appears similar to jira-like:

  • React.
  • Vite.
  • TypeScript.
  • Tailwind/Firebase-style frontend stack.

Important files and folders:

  • jira-like old/jira-like

Business Responsibilities​

Legacy project/task-board behavior. It should not be considered part of the Crimoo GTM product runtime.

Technical Architecture and Source-Code Entry Points​

Use only for historical comparison against jira-like.

Key Data Flows and Service Integrations​

No current production data flow should be inferred from this folder.

Environment, Deploy, and Runtime Notes​

If needed:

cd "jira-like old/jira-like"
npm install
npm run dev
npm run build

Prefer the newer jira-like folder for active work unless the user specifically asks for the old copy.

Debugging Checklist​

  • Confirm the user really means the old copy before editing.
  • Compare against jira-like before porting behavior.
  • Do not treat this as an authoritative source.

Tests or Validation Commands​

cd "jira-like old/jira-like"
npm run build

Mastery Checklist​

  • Identify why this legacy folder exists.
  • Know when to ignore it.
  • Preserve it unless a migration/cleanup task explicitly targets it.