jira-like
Purpose and Production Relevance
jira-like is a separate React/Vite project-management style application. It is not part of the Crimoo GTM runtime, control plane, tracking path, or CRM capture pipeline.
Production relevance: secondary internal/productivity app.
Stack and Main Dependencies
- React.
- Vite.
- TypeScript.
- Tailwind CSS.
- Firebase.
- Radix UI primitives.
- Drag and drop via
@hello-pangea/dnd. - Date utilities and Lucide icons.
Important files and folders:
jira-like/srcjira-like/package.jsonjira-like/firebaseconfiguration where presentjira-like/README.md
Business Responsibilities
Likely responsibilities:
- Track tasks/issues.
- Manage board-like workflows.
- Support team planning or project organization.
This should not be used as a source of truth for Crimoo GTM business logic.
Technical Architecture and Source-Code Entry Points
Vite React app with components, drag/drop board behavior, Firebase integration, and Tailwind styling.
Key Data Flows and Service Integrations
- Browser UI talks to Firebase.
- No documented integration with
node-api,gtm-proxy, orgtm-fabricwas found during inspection.
Environment, Deploy, and Runtime Notes
Common commands:
cd jira-like
npm install
npm run dev
npm run build
npm run deploy
The README mentions Firebase Hosting deployment with hosting:jira-like-crimoo.
Debugging Checklist
- If app fails locally, check Vite config and Firebase environment.
- If deploy fails, check Firebase project/hosting target.
- If drag/drop breaks, check board state and
@hello-pangea/dndIDs. - Do not debug Crimoo tracking/runtime issues here.
Tests or Validation Commands
cd jira-like
npm run build
npm run lint
Mastery Checklist
- Explain why this project is separate from Crimoo GTM core.
- Run and deploy the app if needed.
- Avoid copying product/runtime assumptions from this app into Crimoo core docs.