📋 Backlog
The *Backlog Module is the heart of the application, where all tasks, change requests (CRs), bugs, and feature ideas are logged, managed, and tracked throughout their lifecycle.
Overview
The Backlog module allows project members to manage all work items under their assigned projects.
It provides a powerful Backlog List view with rich filters, sorting, grouping, and search capabilities — and a Create/Edit interface to log or update detailed task information.
This module is permission-driven: access, visibility, and actions (Create, Edit, Close) depend on Project Member mappings and role privileges.
Details / Purpose
The purpose of this module is to provide a centralized task management workspace where users can track project items from creation to closure — maintaining accountability, visibility, and workflow efficiency.
It helps teams:
Maintain a unified view of all project backlogs
Prioritize work based on severity, type, and status
Collaborate efficiently using permissions, filters, and color-coded masters
Monitor reopen counts and overall task health
🔗 Relationship with Other Modules
Module
Purpose / Connection
Project
Each backlog belongs to a specific project.
Task Type
Defines whether an item is a CR, Bug, or To-Do.
Status
Displays workflow progress (e.g., New, InProgress, Resolved, Closed).
Severity
Highlights urgency and impact through color-coded visuals.
Reporter
Identifies who reported or raised the issue.
🗂️ Backlog List View
Overview
The Backlog List View displays all backlog items available to the logged-in user, filtered automatically based on project membership and role-based access.
Each item is visually represented using color codes, icons, and labels defined in the connected master configurations.
🔹 Features
Feature
Description
Color Coding
Uses Text Color, Background Color, and Icon Class from master data (Status, Severity, Task Type).
Reopen Count
Displays how many times the backlog has been reopened, aiding quality and recurrence tracking.
Customizable Columns
Users can select which columns to display, hide, or reorder.
Sorting
Sort by any column (e.g., Created Date, Severity, Status).
Grouping
Group by key columns such as Project, Task Type, or Status for summary-level viewing.
Detailed Filter Panel
Advanced filters covering all related masters — Project, Status, Severity, Reporter, Task Type, Assigned To, etc.
Quick Search
Real-time grid search — typing filters the visible list instantly.
# Search Shortcut
Typing # followed by a task ID (e.g., #1024) filters the specific task immediately on hitting Enter.
Permission-Based Visibility
Only tasks the user is authorized to view (based on project member mapping) are displayed.
Persistent View Settings
User preferences for filters, columns, and sorting are saved for future sessions.
🧭 Example User Flow
User opens the Backlog List page.
The system loads all backlogs linked to projects where the user is a member.
Each backlog row shows severity color, status icon, and reopen count.
The user can filter, search, or group results interactively.
Clicking a row opens the Backlog Edit view for updates.
🖼️ Screenshots
🧾 Backlog Create / Edit Module
Overview
The Create/Edit Backlog interface is where users add or modify work items (CRs, Bugs, To-Dos, etc.). It integrates with all master configurations and applies permission-based controls for each action — Create, Edit, and Close.
🔹 Features
Feature
Description
Master Integration
Connects with Project, Task Type, Severity, Status, and Reporter masters for dynamic dropdowns.
Role-Based Access
Create/Edit/Close permissions controlled by Project Member → Role Privilege mappings.
Parent Task Linking
Option to select a parent backlog item (hierarchical relationship).
Attachments
Upload one or more screenshots or files for visual context.
Comments / Activity Log
Track user discussions and system updates for transparency.
Email Notifications
Triggered automatically via linked Email Template & Email Account.
Auto Reopen Logic
Automatically increments “Reopen Count” when a closed task is reopened.
Audit Trail
Each update records timestamp, user, and change summary.
🧩 Backlog Fields
Field
Description
Project
Project to which this backlog belongs.
Task Type
Defines item category (To-Do / CR / Bug / Nice to Have).
Title
Short title summarizing the issue or request.
Description
Detailed explanation or reproduction steps.
Status
Workflow stage; transitions depend on role privileges.
Severity
Importance or urgency indicator.
Reporter
External or internal individual who raised the issue.
Assigned To
Project member currently responsible for the item.
Parent Task
Optional; links this backlog to another existing item.
Attachments
Screenshots, error logs, or reference files.
Reopen Count
Incremented automatically each time the item reopens.
Created By / On
Automatically populated audit fields.
⚙️ Behaviour Rules:
User must have Create permission to add new backlog items.
Edit and Close actions require specific role privileges.
Status options shown depend on the user’s allowed transitions.
Attachments are stored and versioned per update.
🖼️ Screenshots
⚠️ Notes:
Backlogs cannot be created outside a project.
Permissions are enforced strictly at the Project Member → Role → Privilege level.
Email notifications trigger automatically on Create, Edit, and Close events.
Attachments are optional but recommended for CRs and Bugs.
Reopen count and audit history are system-managed fields and cannot be manually edited.
Last updated