ProgressTracker

ProgressTracker is a comprehensive task management web application that combines powerful task tracking capabilities with AI-driven insights. The application features an intuitive task management interface, data visualization dashboard, and an intelligent chatbot for data analysis.

Key Features

Task Management

• Create, edit, and delete tasks

• Card-based task visualization

• Detailed task tracking with multiple parameters

• AI-driven insights and data analysis

• Search and filter tasks

• Priority and type-based categorization

• Dashboard for task metrics

Dashboard

• Interactive pie charts showing task distribution by:

  • Priority levels

  • Task types

• Line chart visualization for task completion trends

• Real-time progress tracking

AI-Integration

• Intelligent chatbot interface

• Natural language query processing

• Data-driven task analysis

• Trend identification and recommendations

Model Configuration

The application's AI capabilities are powered by a custom-tuned model in Vertex AI Studio. Here's how the model was configured:

• Used Gemini 1.5 Pro, optimized for task management contexts

• Included various query patterns and analytical requests

• Incorporated domain-specific terminology

Model Tuning

• Fine-tuned using Vertex AI's hyperparameter optimization

• Optimized for: Task analysis accuracy Natural language understanding Context-aware responses Data interpretation capabilities

Integration Parameters

• Response temperature: 0.7 (balanced between creativity and accuracy)

• Context window: 2048 tokens

• Custom stop sequences for structured outputs

Frontend Architecture

• React.js for UI components

• Chart.js for data visualization

• Material-UI for component styling

Installation and Setup

Frontend Setup

1. Clone the repository

2. Install dependencies:

   cd frontend
   npm install

3. Run the development server:

   npm run dev

TaskApp System Backend

The backend provides a RESTful API for managing tasks and includes features such as database interaction, logging, and modular route handling.

---

Project Features

• API Endpoints:
  • Fetch all tasks
  • Fetch a single task by ID
  • Query tasks using filters
  • Add, update, and delete tasks
  • Track tasks by JIRA tickets
• Database Integration:
  • MongoDB with Mongoose for schema validation and interaction
• Logging:
  • All API activity is logged
  • Logs stored in a logs.txt file
• Modular Structure:
  • Routes, models, and controllers are separated for maintainability and scalability

---

Technologies Used

Core Technologies

• Node.js: Runtime environment
• Express.js: Framework for building APIs
• MongoDB: NoSQL database
• Mongoose: ODM (Object Data Modeling) library for MongoDB

---

Installation and Setup

Prerequisites

Ensure you have the following installed:

• Node.js: LTS version recommended
• MongoDB: Local or cloud-based instance
• Git: For version control

Steps

1. Clone the repository and navigate to backend:

   git clone <repository-url>
   cd backend

2. Install dependencies:

   npm install

3. Create a .env file with your MongoDB connection string:

   MONGODB_URI=your_mongodb_connection_string
   

   Connection string used here: mongodb+srv://gaurisankar2003:Mongo%[email protected]/Task_App

4. Run the server:

   npm start

Directory Structure

backend/
  ├── models/        # Mongoose schemas
  ├── routes/        # API routes
  ├── controllers/   # Route controllers
  ├── index.js      # Main entry point
  ├── package.json  
  └── .gitignore    

API Endpoints

Task Routes

• GET /api/tasks - Fetch all tasks
• GET /api/tasks/query - Query tasks using filters
• GET /api/tasks/:id - Fetch a task by MongoDB ID
• POST /api/tasks/post - Add a new task
• PUT /api/tasks/update/:jira_ticket - Update a task by JIRA ticket
• DELETE /api/tasks/delete/:jira_ticket - Delete a task by JIRA ticket

Log Routes

• GET /api/logs - Download the API activity log file

Task Schema

Tasks include the following fields:

• task: String (required)
• priority: String (Low/Moderate/High/Critical)
• type: String (Planned/Incidental/Emergency)
• assigned_sp: Number
• actual_sp: Number
• expected_story_points: Number
• actual_story_points: Number
• progress_percentage: Number (0-100)
• status: String (Completed/Under Review/Pending/Yet to be Assigned)
• jira_ticket: String (unique)
• due_date: Date
• department: String
• comment: String