# piyush-eon/jira-clone architecture

> Architecture diagram of the GitHub repository piyush-eon/jira-clone, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-07-09). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/piyush-eon/jira-clone
- Repository: https://github.com/piyush-eon/jira-clone

## Overview

##### Project Type and Purpose
- This is a full-stack, Jira-style issue tracking web application built on Next.js (App Router), React, Tailwind CSS, Prisma (with Neon as Postgres), Clerk for auth, and Shadcn UI components. Users can sign up/in, create organizations, projects, sprints, and issues.

##### Main Architectural Components
a. Client Browser
- Renders React pages and components under the `app/` directory
- Uses Tailwind + Shadcn UI for styling and interactive UI elements
b. Next.js Frontend Layer
- App Router pages (`app/(auth)`, `app/(main)`)
- Client and Server components (e.g., `page.jsx`, `layout.jsx`)
- Static assets (`public/`), global CSS, and data JSON for FAQs, status, companies
c. Authentication Service
- Clerk handles user sign-in/sign-up flows
- Redirects defined in environment variables (`NEXT_PUBLIC_CLERK_*`)
d. API / Business Logic Layer
- Route handlers in `actions/` (issues.js, projects.js, organizations.js, sprints.js)
- Custom server-side utilities (`lib/checkUser.js`, `lib/utils.js`)
- Middleware for auth/session checks (`middleware.js`)
e. Data Access Layer
- Prisma ORM (`prisma/schema.prisma`, migrations)
- Neon (Postgres) database accessed via `lib/prisma.js`
f. Third-Party and Configuration
- Shadcn UI components in `components/ui/`
- eslint, Tailwind, Next.js configs

##### Component Interactions and Data Flows
- User → Browser → Next.js React Components (UI)
- UI triggers fetches or form submissions → Next.js server actions in `actions/`
- Actions validate auth via Clerk & `lib/checkUser.js`, execute CRUD via Prisma → Neon DB
- Responses propagate back up to UI; state updates rerender pages
- Static JSON data read directly by frontend for FAQs, statuses

##### Architectural Patterns and Principles
- Folder-based routing (Next.js App Router) dividing auth vs main flows
- Separation of concerns: UI vs API actions vs data layer
- Single source of truth for data via Prisma ORM models
- Use of middleware for cross-cutting concerns (auth checks)
- Server components handle data loading; client components handle interactivity

## Diagram (Mermaid)

```mermaid
graph TB
    %% Frontend Zone
    subgraph "Frontend" 
        direction TB
        Browser["Client Browser<br/>React + Tailwind + Shadcn UI"]:::frontend
        NextAppRouter["Next.js App Router<br/>app/ (layouts/pages)"]:::frontend
        Components["UI Components<br/>components/"]:::frontend
        StaticAssets["Static Assets<br/>public/"]:::frontend
        DataJSON["Static JSON Data<br/>data/*.json"]:::frontend
        Hooks["Hooks<br/>hooks/use-fetch.js"]:::frontend
    end

    %% Backend/API Zone
    subgraph "Backend/API"
        direction TB
        API_Actions["API Actions<br/>actions/*.js"]:::backend
        Middleware["Middleware<br/>middleware.js"]:::backend
        ServerUtils["Server Utilities<br/>lib/checkUser.js<br/>lib/utils.js"]:::backend
        DataLayer["Data Access Layer<br/>Prisma + Neon"]:::backend
        PrismaClient["Prisma Client<br/>lib/prisma.js"]:::backend
        PrismaSchema["Prisma Schema<br/>prisma/schema.prisma"]:::backend
        Configs["Configuration & Tooling"]:::backend
    end

    %% External Services Zone
    subgraph "External Services"
        direction TB
        ClerkService["Clerk Auth Service"]:::external
        DB["Neon Postgres DB"]:::external
    end

    %% Flows
    Browser --> NextAppRouter
    NextAppRouter --> Components
    NextAppRouter --> StaticAssets
    NextAppRouter --> DataJSON
    Components --> Hooks
    Components -->|form submit / fetch| API_Actions
    API_Actions --> Middleware
    Middleware --> ServerUtils
    API_Actions --> PrismaClient
    ServerUtils --> PrismaClient
    PrismaClient --> PrismaSchema
    PrismaClient --> DB
    Browser -->|auth requests| ClerkService
    API_Actions -->|validate auth| ClerkService

    %% Click Events
    click NextAppRouter "https://github.com/piyush-eon/jira-clone/blob/master/app/layout.js"
    click Components "https://github.com/piyush-eon/jira-clone/tree/master/components/ui/"
    click StaticAssets "https://github.com/piyush-eon/jira-clone/tree/master/public/companies/"
    click DataJSON "https://github.com/piyush-eon/jira-clone/blob/master/data/faqs.json"
    click Hooks "https://github.com/piyush-eon/jira-clone/blob/master/hooks/use-fetch.js"
    click API_Actions "https://github.com/piyush-eon/jira-clone/blob/master/actions/issues.js"
    click Middleware "https://github.com/piyush-eon/jira-clone/blob/master/middleware.js"
    click ServerUtils "https://github.com/piyush-eon/jira-clone/blob/master/lib/checkUser.js"
    click PrismaClient "https://github.com/piyush-eon/jira-clone/blob/master/lib/prisma.js"
    click PrismaSchema "https://github.com/piyush-eon/jira-clone/blob/master/prisma/schema.prisma"
    click ClerkService "https://github.com/piyush-eon/jira-clone/blob/master/next.config.mjs"
    click Configs "https://github.com/piyush-eon/jira-clone/blob/master/tailwind.config.js"

    %% Styles
    classDef frontend fill:#e0f2ff,stroke:#0369a1,color:#0369a1;
    classDef backend fill:#dcfce7,stroke:#15803d,color:#166534;
    classDef external fill:#ffedd5,stroke:#ea580c,color:#b45309;
```
