Task Details Page

This guide explains how to operate the Task Details pages in Productized Services for WooCommerce:

/wp-admin/admin.php?page=psfw-task-manage&task_id=365

Use this page to update a task’s ownership, workflow status, deadline, project placement, comments, and (optionally) attachments/time logging.

What This Page Is For #

The Task Details pages are the control center for one task.

Use them to:

  • update task content (title and description)
  • assign responsibility and collaborators
  • set status, priority, and due date
  • move the task to a different project
  • review internal coordination notes and activity signals
  • perform controlled task deletion when truly necessary

Access and Permissions #

The page requires Productized Services admin/task access.

Capability rules affect what each user can do:

  • users without task edit access cannot use this page
  • reassignment controls depend on task reassignment capability
  • delete actions require task delete access
  • customer assignment/collaborators/attachments/time logging can depend on Pro hooks

If a field is disabled or missing, check role/capability mapping before troubleshooting data.

Page Structure and Navigation #

The page has:

  • heading: Manage Task #ID
  • back button: Back to Tasks or Back to Project #ID (when opened from a project)
  • tab navigation:
    • Overview
    • Time Tracking
    • Details
  • persistent sidebar (Status, Priority, Due Date, Save)

Save and Tab Behavior #

When you click another tab with unsaved edits, the form submits first so changes are preserved.

Important save safeguards:

  • nonce validation protects submit actions
  • stale-edit detection blocks overwriting if another user saved first
  • invalid due date input is rejected with an error notice

Recommendation:

  • when you see a “modified by another user” notice, reload first, then re-apply your intended change.

Status #

Status options are normalized to the task status set:

  • To Do (to-do)
  • In Progress (in-progress)
  • In Review (in-review)
  • Done (done)
  • Blocked (blocked)
  • Canceled (canceled)

Recommendation:

  • use Blocked instead of leaving blocked work in In Progress, so triage and reporting stay accurate.

Priority #

Priority options are:

  • Low
  • Medium
  • High

Recommendation:

  • reserve High for true time-critical or dependency-critical work to keep priority meaningful.

Due Date #

The field uses date/time input (datetime-local).

Recommendation:

  • always set a due date for production tasks; leave empty only for backlog items with no committed schedule.

Save Changes #

Use Save changes after edits. On success, the page reloads with a success notice and keeps you on the submitted tab.

Overview Tab #

The Overview tab is best for execution updates and team coordination.

Task Details Card #

Task Title #

Required field.

Recommendation:

  • use action-oriented titles (verb + deliverable), for example: “Draft homepage hero copy”.

Description #

Use this for scope, acceptance details, references, and context.

Recommendation:

  • include clear “done criteria” so assignee and reviewer use the same quality bar.

Assignment Card #

Assignee Type #

Depending on setup, assignment can target:

  • internal assignee
  • customer assignee (when customer assignment support is active)

Assignee #

Choose who is responsible. Includes Unassigned.

Recommendation:

  • keep this field non-empty for active tasks; unassigned tasks should be temporary only.

Visible to Customer #

Controls whether the task is client-visible.

Notes:

  • may be disabled in Free mode
  • is disabled when no project is selected

Recommendation:

  • set to No for internal coordination tasks; set to Yes only for customer-relevant work.

Collaborators #

Collaborators UI is available when Pro collaborators support is active.

Recommendation:

  • add collaborators only when they actively contribute, to avoid noisy access and unclear accountability.

Internal Comments Card #

Internal comments are staff/admin-facing only and not customer-visible.

Use this area for:

  • implementation notes
  • handoff context
  • blockers and next actions

Recommendation:

  • keep comments operational (what changed, why, and what is next), not conversational.

Activity Log Card #

In Free mode, this appears as an upgrade CTA preview.

In Pro-enabled setups, this area can show meaningful change history (status/assignment/time edits).

Recommendation:

  • rely on this stream during incident reviews and ownership disputes instead of memory-based reconstruction.

Time Tracking Tab #

The Time Tracking tab is focused on effort planning and effort monitoring.

Estimated Time #

Use hours + minutes inputs.

Recommendation:

  • estimate in realistic delivery units (for example 1h 30m, not broad placeholders like “sometime today”).

Logged Time #

In Free mode, this area is a Pro CTA.

In Pro-enabled setups, use logged time to capture actual effort.

Recommendation:

  • update logged time during or immediately after work blocks to keep data reliable.

Time Progress #

In Free mode, this area is a Pro CTA.

In Pro-enabled setups, this helps compare logged effort vs estimated effort.

Recommendation:

  • investigate repeated overrun patterns and adjust future estimates or process constraints.

Details Tab #

The Details tab is for structural task administration.

Project Card #

Project #

Assign task to:

  • a specific project
  • No Project

Recommendation:

  • keep production tasks attached to a project whenever possible so workload and reporting stay grouped correctly.

Attachments Card #

In Free mode, this appears as a Pro CTA.

In Pro-enabled setups, this is where task file attachments are managed.

Recommendation:

  • attach only task-relevant assets and keep naming consistent to reduce retrieval time.

Delete Task Card and Modal #

Delete is permanent and uses a confirmation modal.

Flow:

  1. Click Delete in the card.
  2. Confirm in modal (Confirm deletion) or cancel.

Recommendation:

  • delete only duplicate or invalid tasks. Prefer updating status/assignee/project for legitimate historical tasks.
  1. Open task from queue and confirm title/description clarity.
  2. Set status and priority in sidebar.
  3. Verify assignee and visibility in Overview.
  4. Update internal comments with concise operational notes.
  5. Confirm due date and save.
  6. Use Details tab only when project mapping or deletion is required.

Common Mistakes and Fixes #

Mistake: Editing Only Status Without Updating Ownership #

Impact:

  • tasks look active but accountability is unclear

Fix:

  • always pair status change with an assignee check.

Mistake: Using High Priority Too Broadly #

Impact:

  • priority loses meaning and triage degrades

Fix:

  • keep High limited to true urgency/dependency work.

Mistake: Deleting Tasks Instead of Correcting Metadata #

Impact:

  • lost operational history

Fix:

  • prefer reassignment/restatus/project correction before deletion.

Mistake: Ignoring Stale-Edit Warning #

Impact:

  • attempted overwrite fails and users repeat edits

Fix:

  • reload immediately, review latest values, then save again.

Troubleshooting #

I Can’t Save Changes #

Check:

  • required title is not empty
  • due date format is valid
  • nonce/session has not expired (reload and retry)
  • record was not updated by another user while page was open

Visibility Option Is Disabled #

Likely causes:

  • no project selected
  • Free mode limitations for customer-facing controls

Customer/Collaborator Assignment Controls Are Missing #

Likely cause:

  • Pro assignment hooks are not active in this setup

Delete Button Is Missing #

Likely cause:

  • current user lacks task delete capability

Summary #

The Task Details pages are where task execution quality is enforced in Productized Services.

When teams consistently maintain status, ownership, visibility, due dates, and comments on this page, delivery becomes easier to coordinate, audit, and scale.

What are your feelings

Updated on March 3, 2026