Bug Tracking System

Features

Industries

Reference

More

Start now
  1. Bug Tracking System
  2. Process
  3. Submit and Validate Time
Process · Submit and Validate Time

Submit and Validate Time

Book corrective effort and inspect the automatic approval result and any failed attempt.

Start now Download Proto

Step by step

  1. Record the effort Developer

    Developer creates a Draft time entry with the work date, hours, team member and project. Link the corrective task where appropriate and describe the work performed. Check its project context before relying on the entry in a delivery review.

    • Prepare dated effort against the correct project
    • Updates Time entries, Tasks, Projects, Team members

  2. Submit the entry Developer

    Developer marks the prepared entry Submitted. Confirm the hours are positive and that the description explains the effort. Billable or Non-Billable follows the operating definition agreed by the team.

    • Move Draft to Submitted
    • Updates Time entries

  3. Apply validation Developer

    The Time Entry Approval workflow checks that the entry is still Submitted and its hours are positive. A successful check automatically moves it to Approved and records a review decision and operation receipt. This action does not require a separate human approval stage.

    • Automatically approve only positive hours still Submitted
    • Updates Time entries, Review decisions, Operation receipts

  4. Investigate a failed attempt Developer or Project Manager

    Project Manager and Developer inspect the receipt and source entry when a guard fails. Zero or negative hours do not qualify for approval. An entry that is no longer Submitted also fails the check. Preserve the failed-attempt evidence while resolving the underlying cause.

    • Explain invalid hours or an ineligible source state
    • Updates Time entries, Operation receipts

  5. Review the effort position Project Manager or Delivery Lead

    Project Manager compares accepted and outstanding entries with task and project context. Delivery Lead uses the resulting workload discussion alongside team capacity. Keep booked time distinct from task actual hours unless the agreed calculation explicitly connects them.

    • Compare recorded effort and workload in context
    • Updates Time entries, Tasks, Projects, Team members

Where it usually breaks

And how to keep it from happening.

  • The selected task belongs to another project. Correct the reference before interpreting the time as project effort.
  • An entry is submitted with nonpositive hours. Inspect the failed result and prepare a valid correction.
  • A failed operation is described as a Rejected entry. Check the actual entry state; the receipt result alone does not establish that transition.
  • All assigned task estimates are treated as this week's workload. Check task dates before comparing them with weekly capacity.

Who does what

Roles and permissions
Developer
, Project Manager, Delivery Lead.

Set up Bug Tracking System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

Start now Download Proto

How to get started