TM - Tasks
The Task Manager module is designed to help users efficiently plan, organize, and track tasks within a selected Organization, Business Unit, and Project. It provides a centralized grid-based interface where all task-related information -such as planned dates, actual progress, hierarchy, and completion status-can be viewed and managed in one place.
The module is built to support real-time updates, allowing users to directly edit and manage tasks without navigating across multiple screens. It also supports hierarchical task structures, enabling users to group related tasks under parent tasks for better organization and tracking.
Accessing the Task Manager
To access the Task Manager, navigate through the application menu:
Home > Task Management > Task Manager
Once selected, the Task Manager page opens with a structured layout that allows users to begin working immediately.
Task Editor - Understanding the Page Layout
When the Task Manager page opens, the screen is divided into three main sections.
On the left side, there is a navigation panel that allows users to switch between different modules such as Dashboard, Project Summary, Resource Summary, and Configuration.
At the top of the page, users must select the Organization, Business Unit, and Project. These selections are mandatory and act as filters. Only the tasks relevant to the selected values will be displayed in the grid.
The main area of the screen displays the Task Grid, which is where all task-related operations are performed.
Working with the Task Grid
The Task Grid is the central working area of the module. Each row in the grid represents a task. Tasks can either exist independently or be structured under a parent task to form a hierarchy.
Parent tasks are visually distinguishable by appearing in bold, and users can expand or collapse them to view or hide their child tasks. This makes it easier to manage large sets of tasks without cluttering the screen.
The grid supports inline editing, which means users can directly click on any editable cell and update its value without opening a separate screen. All updates reflect immediately, making task management fast and efficient.
Using Grid Controls
At the top of the grid, users will find a set of controls that allow them to perform different actions.
On the left side, options such as Add New Row, Save All Rows, Indent, and Outdent are available. These controls help users create new tasks, save changes, and manage task hierarchy.
The Add New Row option allows users to insert a new task directly into the grid. Additionally, users can also insert tasks between existing rows using a plus (+) icon, providing a seamless experience like Loop-style editing.
Indent and Outdent options are used to structure tasks. Indenting a task makes it a child of the task above, while outdenting removes that relationship.
On the right side, users will find options such as Create New Task, Search, Filter, Column Visibility, Export, and Settings. These controls help users quickly locate tasks, customize their view, and manage data efficiently.
Creating a New Task
To create a new task, users can click on the Create New Task option available at the top of the grid. This opens a popup window where task details can be entered.
The Work Item field is mandatory and must be filled before saving the task. Once all required details are entered, clicking on the Save button creates the task and adds it to the grid.
If the user decides not to create the task, they can close the popup using the close (X) icon, and no data will be saved.
Managing Task Hierarchy
Tasks in the grid can be structured in a parent–child format to represent dependencies or grouped work.
When a task is indented, it becomes a child of the task above it. This allows users to organize tasks logically under broader categories. Outdenting a task removes it from the hierarchy and makes it an independent task.
This structure helps in better visualization and tracking of related work items.
Tracking Task Progress
The system provides a flexible way to track task completion using the % Complete field.
The value can be automatically calculated based on work logs entered by the assignee. This system-calculated value is displayed in gray, indicating that it is derived from actual work.
Managers also have the ability to override this value by entering a manual percentage. This overridden value is displayed in black, and the original calculated value is shown in brackets for reference.
This approach ensures transparency while allowing flexibility in progress tracking.
Understanding Dates and Duration
The system automatically manages Actual Start Date, Actual End Date, and Actual Duration based on work logs.
The Actual Start Date is populated when work begins on a task, and the Actual End Date is populated when the task is 100% completed. The Actual Duration reflects the total effort spent.
The system also calculates slippage, which is the difference between the planned end date and the actual end date. This helps users identify delays in task completion.
Default Task behaviour
Whenever a new task is created or inserted into the grid, its status is automatically set to Backlog. This ensures that all new tasks are tracked from a consistent starting point.
Users can later update the status based on progress.
Working with Attachments
Within the Task Editor popup, users have the option to attach files related to the task.
Users can upload, view, or delete attachments. Each attachment includes details such as file name, size, date, and the user who uploaded it.
This helps in maintaining all relevant task-related documents in one place.
Using Filters and Search
To quickly locate tasks, users can use the search bar available at the top of the grid.
Additionally, the filter option allows users to define specific conditions and apply them to the grid. Filters can also be saved for future use, making it easier to repeatedly access filtered data.
Row-Level Actions
Each task row provides additional actions through a right-click menu or action icon.
Users can copy, paste, delete, or insert rows above or below. If a task has child tasks, the system prompts the user for confirmation before deletion to prevent accidental data loss.
Users can also access task history to view past changes.
Assigning Tasks
Tasks can be assigned to team members using the Assignee field. The available users are populated based on the selected project, business unit, and organization cluster.
This ensures that only relevant users are available for assignment.
1 Task Grid & Filter Functionality
The Task Grid has been enhanced to provide a more interactive, efficient, and user-friendly experience. These improvements help users manage tasks more effectively through better navigation, editing capabilities, and advanced filtering options.
Along with grid improvements, a powerful filtering system is introduced that allows users to quickly find relevant data, save filter configurations, and reuse them whenever required.
Working with the Enhanced Task Grid
The Task Grid is designed to behave more like a smart spreadsheet, making it easier for users to manage large sets of task data.
Users can now work with tasks in a hierarchical structure where parent and child relationships are clearly maintained. Tasks are automatically numbered in both hierarchical and sequential formats, making it easier to track their position within the structure.
Editing tasks has become more intuitive. Users can directly update values within the grid, and navigation across cells is smoother using keyboard actions such as Tab to move forward and Delete to clear values, like Excel.
Users can also use:
Ctrl + D to quickly fill values down a column
Ctrl + C / Ctrl + V (restricted where required to maintain data integrity)
A) Ctrl + D to quickly fill values down a column:
B) Ctrl + C OR Ctrl + V (restricted where required to maintain data integrity):
The grid also allows users to rearrange tasks easily using drag-and-drop functionality. This makes it simple to reorder tasks or move them within different levels of the hierarchy.
An enhanced action area is available near the search bar, where additional controls such as buttons, toggles, or custom actions can be accessed. This provides quick access to frequently used operations without cluttering the grid.
Users can perform advanced searches using logical conditions such as AND and OR, allowing more precise results when working with large datasets.
When exporting data, the system ensures that the exported Excel file retains proper data types based on the input fields, making it more usable for reporting and analysis.
Using Filters in the Task Grid
To help users quickly find relevant information, the grid provides a powerful filtering option. The Filter icon is available at the top-right corner of the grid, next to the search bar. Clicking on this icon opens the Filter Panel.
Applying Filters
Users can create filters by selecting a field and defining conditions based on that field.
For example, a user may want to:
- View only tasks assigned to a specific person
- Check tasks with a particular status
- Find tasks within a certain date range
Once the filter conditions are applied, the grid automatically refreshes to show only matching records.
Working with Different Types of Filters
The filtering experience adapts based on the type of data in the selected field.
For text-based fields such as Work Item or Predecessor, users can enter values manually and apply conditions like “contains” or “starts with.” For dropdown-based fields such as Status, Priority, or Assignee, users can select values from a predefined list. Multiple selections are supported, allowing users to filter more flexibly.
For date fields, users can either select dates from a calendar or enter them manually in the required format. If a range is selected, both start and end dates must be provided.
For percentage-based fields like % Complete, users can enter values or define ranges to filter tasks accordingly.
Saving Filters for Reuse
One of the key features of the filtering system is the ability to save filters.
After defining filter conditions, users can assign a name to the filter and save it. This allows them to reuse the same filter later without redefining conditions. Once saved, the filter becomes available in the filter dropdown and can be applied anytime.
Using Saved Filters
Users can select any previously saved filter from the dropdown. Once selected, the system automatically applies the stored conditions and refreshes the grid.
This is especially useful for frequently used views, such as:
- “My Tasks”
- “High Priority Tasks”
- “Pending Tasks This Week”
Updating Existing Filters
If users want to modify a saved filter, they can update the conditions and click Update Filter. If the update is not saved, the changes will only apply temporarily and will not overwrite the original filter.
Clearing Filters
Users can remove all applied filters using the Remove All Filters option.
This resets the grid to its default view, showing all records. However, saved filters remain available and are not deleted.
2 File Attachment Management
The Attachments feature helps you easily add and manage files related to your work items. Whether you are creating a new task or editing an existing one, this feature ensures that all your important documents stay linked and accessible in one place.
You can use this feature to:
- Attach supporting documents while creating a task
- Add or update files while editing a work item
- Quickly view or preview files anytime
This consistent experience makes it easier to manage attachments throughout the entire lifecycle of a work item.
The Attachments section is available in both:
- View work log (while viewing a work item)
- Work Item Editor (while editing a work item)
In both cases, the section is placed just below the work item details panel, so it is easy to locate and use.
Attachments Feature
The Attachments feature allows you to:
- Add new files
- View already attached files
- Remove unwanted files
- Save your attachment changes
All these actions are available both during task creation and while editing, ensuring a smooth and consistent experience.
Add Attachments
To attach files to your work item:
- Click on the Attachment icon or Add Attachment option
- A popup window will open where you can select and manage files
Inside the Popup
You will see:
- A Browse option to select files from your system
- A Comments field to add notes about the file
- OK button to confirm upload
- Cancel button to discard changes
- Close (X) icon to exit the popup
If you click Cancel or close the popup, no files will be saved or uploaded.
Selecting Files
You can easily select files from your local system using the Browse option.
Important Points to Remember:
- You must select at least one file to proceed
- You can select multiple files at once (up to 50 files)
- If you select more than 50 files, you will see an error message
If you add many files and they don’t fit in the popup, a scrollbar will automatically appear for easy navigation.
File Validation Rules
To ensure smooth operation, the system checks your files before adding them:
- Duplicate files are not allowed
- Unsupported file types will be rejected
Unsupported formats include:
- Images
- ZIP files
- APK files
- Audio/Video files
- Folders
If any invalid file is selected, a temporary error message will be shown and the file will not be added.
Draft Mode Before Upload
When you select files:
- They will appear immediately in the popup
- They are added as a draft list
- Files are not uploaded yet
Files will only be uploaded after you click the OK button.
This helps you review and make changes before final submission.
Viewing Attachment Details
Once files are added, you can see important details such as:
- File Name
- File Size
- Date Attached
- Added By (Username)
- Comments
Additional UI Features:
- Each file shows a file-type icon
- Long file names are shortened with
- Hovering over the name shows the full file name
Quick Access from Work Item
You don’t always need to scroll to the Attachments section.
A File Attachment icon is available in the work item area, allowing you to:
- Quickly open the attachment popup
- Add or view files instantly
This works the same way in both View work log and Edit screens.
Working with Attached Files
You can interact with your files using simple actions:
Remove File
- Click the Remove icon to delete a file from the list
Preview File
- Click the Preview (eye icon) to open the file
Preview Features:
- Zoom in and zoom out
- Full-screen mode
- Exit preview using the ESC key
Uploading Files
Once you are ready:
- Click OK or Attach
- All selected draft files will be uploaded
- Files will be linked to the work item
After successful upload:
- The corresponding row will be highlighted visually
Editing Existing Attachments
When you open an existing work item:
- All previously attached files will be visible
- You can add new files or remove existing ones
If you try to upload a file that already exists, the system will show an error and prevent duplication.
Saving and Persistence
All your attachments are reliable:
- Files remain attached after saving the work item
- Attachments are available when you reopen the task
- No data is lost between sessions
This ensures that all your important documents stay securely linked to your work item.
3 Task History
The Task History feature allows users to view the complete history of a task from creation to the latest update. It helps users understand what changes were made, who made them, and when they occurred.
This ensures full transparency and makes it easy to track task updates, review past changes, and support audit or troubleshooting activities.
Accessing Task History
Users can open Task History from multiple places:
- Right-click on a task row > Task History
- Task Editor > Task History tab
- Work Log view > Task History tab
Understanding the Task History View
The Task History opens in a grid format where each row represents a change or activity related to the task.
- The latest changes appear at the top
- Older changes appear below
- Each entry shows the timeline of updates clearly
What Information is Shown
Each history record includes:
- Task name and change description
- User who made the change
- Date and time of the change
- Updated values such as status, dates, priority, assignee, etc.
- Type of event (e.g., status update, date change, reassignment)
Changed values are clearly highlighted for better visibility.
Using Search and Navigation
Users can quickly find specific history records using the Quick Search option.
- Search by user name, change type, or keywords
- Results update instantly
The Reset option clears the search and returns to the first page.
Pagination and Record Count
If there are many records:
- Data is divided into pages
- Users can navigate using page numbers or next/previous buttons
A record count is displayed (e.g., Showing 1–10 of 50 records) to help users understand how many changes are available.
Exporting Task History
Users can download the history data using the Export option.
- Data is exported in Excel format
- Useful for reporting, audits, or offline review
Important Behaviour
- Task History is read-only
- Records are automatically created by the system
- No record can be edited or deleted
- Every change (manual or system-generated) is captured
- Data is always shown in chronological order (latest first)
4 Planned Dates Roll-up & Editing Behaviour
The Planned Start Date and Planned End Date of parent tasks are automatically managed by the system based on their child and sub-child tasks.
This ensures that parent tasks always accurately reflect the timeline of all underlying work. At the same time, users are allowed to adjust parent task dates within certain limits to support planning flexibility.
How Parent Task Dates Work
For any parent task, the system automatically calculates dates based on its child tasks.
- The Planned Start Date is set to the earliest start date among all child and sub-child tasks
- The Planned End Date is set to the latest end date among all child and sub-child tasks
This automatic calculation is known as roll-up, and it ensures that the parent task always represents the full duration of all its children.
Automatic Updates Based on Changes
Whenever there is any change in the task hierarchy, the system updates parent task dates automatically.
This includes situations such as:
- Adding a new child or sub-child task
- Updating the planned dates of an existing child task
In such cases, the parent task dates are recalculated to reflect the latest timeline.
Editing Parent Task Dates
Users are allowed to edit the Planned Start Date and Planned End Date of parent tasks, but only within valid limits.
Users can:
- Set a start date earlier than the earliest child task
- Set an end date later than the latest child task
This allows users to expand the timeline of a parent task if required for planning purposes.
Restrictions While Editing
While editing is allowed, the system ensures that parent tasks always cover all child tasks.
Users cannot:
- Set a start date later than any child task
- Set an end date earlier than any child task
If such a change is attempted, the system will block the update and display a validation message.
System Behaviour and Priority
It is important to note that:
- Parent task dates are primarily controlled by the system
- Any manual changes made by users are considered temporary
- If child task data changes, the system will override manual values
This means the roll-up logic always ensures consistency and accuracy across the task hierarchy.
User Awareness
To avoid confusion, users should be aware that parent task dates are dynamic and depend on child tasks.
In scenarios where child tasks are updated or new tasks are added, parent dates may automatically change even if they were manually edited earlier.
A typical system message or tooltip may indicate:
“Parent task dates are automatically adjusted based on child tasks.”
5 Planned Dates Change Approval & Communication
To ensure better control, transparency, and accountability in task planning, any change to the Planned Start Date or Planned End Date follows an approval process.
Instead of updating dates directly, the system captures the request, allows discussion through Chatbot, and updates the task only after approval. This ensures that all changes are tracked, reviewed, and properly documented.
How Planned Date Changes Work
When a user attempts to update Planned Dates, the system does not immediately apply the change.
Instead:
- A change request is created
- The existing dates remain unchanged
- The task continues to be editable for other fields
This ensures that date changes are controlled and reviewed before being finalized.
Viewing Pending Date Changes
When a date change is under approval, users can view details directly on the task without opening a separate screen.
By hovering over the Planned Date field, the following information is displayed:
- Existing Planned Dates
- Requested New Date
- Requested By
- Requested On
- Reason for Change
This allows quick visibility and helps users understand the context of the change.
Approval and Rejection Process
Authorized users (such as Project Managers or Admins) can take action on the request.
- Approve - Accept the requested change
- Reject - Decline the request
These options are available on hover for authorized users. Other users can only view the request.
What Happens on Approval
When a request is approved:
- Planned Dates are updated to the new values
- Task timelines are recalculated (if applicable)
- The action is recorded in Task History
What Happens on Rejection
When a request is rejected:
- Planned Dates remain unchanged
- A rejection reason must be provided
- The action is recorded in Task History
Using Chatbot for Discussion
Before approving or rejecting a request, users can communicate directly through the Chatbot.
When a discussion is required:
- A Chat icon appears on the task row
- Clicking it opens a side chat panel
- Users can discuss the change, clarify reasons, and make decisions
This avoids unnecessary emails and keeps all communication linked to the task.
How the Chat Flow Works
- Assignee requests a date change and provides a reason
- Manager reviews the request
- If needed, discussion happens through Chatbot
- Final decision is taken (Approve OR Reject)
- Decision is applied and recorded
All conversations and actions are stored for future reference.
Notifications
To keep users informed without overwhelming them:
- The system sends one consolidated email
- Notifications are triggered when:
- A date change request is created
- A request is approved or rejected
Tracking Changes in Task History
All actions related to Planned Date changes are recorded in Task History.
This includes:
- Requested changes
- Approval or rejection decisions
- User details and timestamps
- Related remarks and events
This ensures complete traceability of all decisions.
6 Actual Dates and Roll-up Functionality
The roll-up functionality helps users easily track overall task progress without manually updating parent tasks. Whenever work is done on child tasks, the system automatically updates the parent task’s Actual Start Date, Actual End Date, and Actual Duration.
This ensures that the parent task always reflects the latest progress happening within its hierarchy.
How Actual Dates Work
The Actual Start Date of a parent task is automatically set to the earliest start date among all its child tasks or the parent’s own work log, whichever is earlier. This means the parent task always shows when work began across the entire hierarchy.
Example:
If one child task starts on 05 Jan, another on 08 Jan, and the parent has work logged on 07 Jan, the parent task will show 05 Jan as the Actual Start Date.
The Actual End Date is calculated based on the latest completion date among child tasks or the parent’s own work log. However, this date will only appear when all child tasks are completed, and the parent task is also marked as 100% complete.
If even one child task is incomplete, the parent task will not display an Actual End Date.
Example:
If child tasks are completed on 10 Feb and 11 Feb, the parent task will show 11 Feb as the Actual End Date once everything is completed.
The Actual Duration of a parent task is the total of all time logged across its child tasks along with any work logged directly on the parent. This gives a complete view of the total effort spent.
How the System Updates Automatically
The roll-up values are updated automatically whenever changes happen in the task. This includes adding, editing, or deleting work logs, updating completion percentage, restructuring tasks (like indenting or dragging), or marking tasks as complete or incomplete.
Users do not need to refresh or manually update anything-the system keeps everything in sync.
What Happens in Different Scenarios
When some child tasks are completed but others are still pending, the parent task will still show the correct start date and total duration, but the Actual End Date will remain blank. This ensures that completion is only reflected when all work is finished.
If a completed child task is reopened, the parent task will automatically remove its Actual End Date and adjust its completion status accordingly.
When work logs are added to child tasks, the parent task’s duration increases automatically. Similarly, if work logs are deleted, the parent duration decreases accordingly.
If tasks are moved, indented, or reorganized, the system recalculates the roll-up values based on the updated structure.
Important User Guidelines
When copying tasks or inserting new rows, the Actual Start Date and Actual End Date are not copied. These fields will remain blank in the new row to avoid incorrect data.
When tasks are moved using drag-and-drop, the system ensures that actual dates are duplicated, and existing task data remains unchanged.
The Chatbot (Messaging Module) is designed to enable seamless communication and collaboration within the application. It allows users to connect with team members, discuss tasks, and stay aligned without relying on external tools.
With this feature, users can send direct messages, participate in group discussions, and communicate within the context of tasks or work items. This helps in keeping all conversations, decisions, and updates centralized within the system.
Accessing the Chatbot
The Chatbot is designed to be easily accessible from multiple areas so that users can communicate without interrupting their workflow.
Users can access it through the main navigation by going to:
Work Item > Work Log > Chatbot
Additionally, a Chat icon is available at the top-right corner of the screen. Clicking on this icon opens the Chatbot in a side panel, allowing users to quickly view and respond to messages without leaving the current page.
The Chatbot is also available while working in different areas of the system. For example, while editing a task or reviewing work logs, users can continue conversations without navigating away. This ensures that communication remains part of the workflow.
In certain views, such as task hierarchy or work item screens, users can access Chat through the ellipsis menu (…). Selecting the Chat option opens the Chatbot with context linked to that specific task or item, making discussions more relevant.
Understanding the Chatbot Interface
The Chatbot interface is divided into three main areas to make communication simple and organized.
On the left side, users will find a panel that lists conversations, including direct messages and channels. The central area displays the selected conversation, and at the bottom, there is a message box where users can type and send messages.
Working with Direct Messages
Direct Messages allow users to have one-to-one conversations.
In the Messages section, users can see a list of all their conversations. Each entry shows the user’s name, profile icon, and status. Clicking on any conversation opens the chat history.
Users can start a new conversation by clicking the plus (+) icon in the Messages section. This opens a popup where users can search and select another user to begin chatting.
This makes it easy to quickly connect with team members and maintain continuous communication.
Using Channels for Group Discussions
Channels are used for group conversations. They are useful when multiple users need to collaborate on a common topic, such as a project or team discussion.
Examples of channels may include:
- Development Team
- Database Team
- Work Item Discussions
Users can create a new channel by clicking the plus (+) icon in the Channels section. A popup will appear where the user needs to enter a Channel Name (mandatory) and can optionally add a description.
Once created, channels allow all members to participate in discussions, making communication more structured and organized.
Managing Channels
Each channel provides additional options through an ellipsis menu (…).
Users can:
- Start a thread within the channel for focused discussions
- Edit channel details such as name or description
- Delete the channel if it is no longer required
These options help in keeping conversations organized and relevant.
Working with Threads
Threads allow users to have discussions related to a specific topic within a channel.
For example, if a team is discussing multiple tasks, each task can have its own thread. This helps in avoiding confusion and keeps conversations structured.
Threads can also be linked to specific tasks or work items, allowing users to track discussions in context.
Searching in Chatbot
The Chatbot provides a search feature that allows users to quickly find:
- Users
- Conversations
- Messages
This is especially helpful when users want to revisit past discussions or locate specific information.
Sending Messages
At the bottom of the chat window, users will find the message input area.
Users can:
- Type messages
- Use emojis
- Send messages instantly
The interface is simple and intuitive, ensuring smooth communication.
How Chat Works in Real Scenarios
When users open Chat from a task or work item, the conversation is linked to that specific context. This helps teams discuss work directly where it is happening.
If a task is deleted or archived, the Chatbot will indicate this status, ensuring users are aware of changes.
Recent activity related to a task may also be displayed at the top of the conversation, helping users quickly understand the latest updates.
Important Behaviours to Note
- Messages are saved automatically and remain available even after logging out
- Conversations are displayed in chronological order
- Channels and threads help organize discussions
- Some actions (like deleting channels) may depend on user permissions
- Closing popups without saving will discard changes
Summary
The Chatbot module helps users stay connected and collaborate efficiently within the application.
It allows users to:
- Communicate in real time
- Discuss tasks within context
- Maintain conversation history
- Collaborate through channels and threads
By integrating communication directly into the workflow, the Chatbot reduces dependency on external tools and improves overall productivity.
8 Work Log & Timesheet Synchronization
1. Purpose
The purpose of this functionality is to ensure that Work Log entries and their descriptions remain fully synchronized with the Timesheet view. This helps maintain:
- Accurate hour calculations
- Consistent task-level details
- Prevention of accidental data loss during edits
This ensures users always see reliable and consistent data across all related views.
2. Synchronization Scope
Synchronization is maintained across the following components:
- Work Log Page
- Timesheet View (Time Port)
- Task Editor (where applicable)
Important:
Any update made in one view must reflect consistently across all other views.
3. Timesheet (Time Port) Display Behaviour
When a user logs multiple entries for the same task (for example, 5 entries totalling 5 hours), the Timesheet must display each entry individually.
Expected Behaviour
- Each work log entry appears as a separate row
- Each entry retains:
- Its original logged hours
- Its description
- Its timestamp-order
- There should be no aggregation of hours at:
- Task level
- Day level
System Rules
- The Timesheet must reflect Work Log entries exactly as recorded
- The order of entries must remain unchanged to maintain traceability
Descriptions entered in Work Logs must be accurately displayed in the Timesheet.
Structure
- Task Title Column: Displays the task name
- Description Column: Displays the work log description
Expected Behaviour
- Each work log entry must show its own description
- Descriptions must not:
- Be overwritten
- Be merged
- Be lost
System Rules
- Description data must always remain linked to its specific work log entry
- The system must preserve descriptions during all operations (viewing, editing, syncing)
Users can edit work log descriptions from:
- Timesheet view
- Task Editor
Expected Behaviour
- Changes are saved successfully
- Updates are reflected immediately across:
- Work Log page
- Timesheet view
System Rules
- All updates must remain consistent across all synchronized views
- There should be no mismatch between Work Log and Timesheet data
To prevent accidental removal of descriptions, the system enforces the following behaviour:
If a user clears a description
- Before saving, the system will:
- Automatically restore the previous description
- Fetch it from the Work Log page
Final Save Validation
- The system ensures:
- Descriptions are not removed unintentionally
- Any change or removal must be explicitly confirmed by the user
Important Constraints
- Work log descriptions must never be lost during editing
- Data integrity must always be maintained across all views
To maintain accurate tracking:
- Start Time and End Time must not overlap for the same user on the same day
- Each work log entry must represent a valid and non-conflicting time range
System Constraints
- Overlapping entries are not allowed
- All time validations are system-controlled
The following fields are automatically calculated by the system:
- % Complete
- Total Logged Hours
- Actual Start Date
- Actual End Date
Behaviour
- Progress is calculated using the latest work log entries per assignee
- A task is marked complete only when:
- All assignees reach 100% completion
Important Rules
- These values are read-only
- Users cannot manually override or edit them
- All calculations are system-driven and auditable
To ensure consistency:
- Work Log and Timesheet data must always remain fully synchronized
- Any update in one module must reflect in all other related modules
System Rules
- No data mismatch should occur between views
- All updates must be processed in real time or near real time
This functionality ensures:
- Accurate and detailed tracking of individual work log entries
- Complete synchronization across Work Log, Timesheet, and Task Editor
- Strong data protection to prevent accidental loss
- System-controlled calculations for reliability and auditability
It is designed to provide a consistent, transparent, and reliable time tracking experience for all users.