Deleting a Task

This guide explains how to delete tasks safely in Productized Services for WooCommerce, including when to delete, how to delete, and what happens after deletion.

Why This Matters #

Task deletion is a powerful cleanup feature for keeping your workspace accurate.

Benefits of correct deletion usage:

  • removes accidental or duplicate tasks
  • keeps task lists cleaner for teams
  • reduces reporting noise from invalid records

Before You Delete: When Deletion Is the Right Choice #

Use deletion when a task is truly invalid, such as:

  • duplicate task created by mistake
  • test/sandbox task in production view
  • task created in wrong context and no longer needed

Prefer updating (instead of deleting) when the task represents real delivery history.

Single-Task Deletion (Task Details Page) #

Single-task deletion is available from the task manage screen.

Where to Find It #

Go to:

  • task details page
  • Details tab
  • Delete Task card

What You See #

The card includes:

  • warning text that deletion is permanent
  • Delete button
  • confirmation modal with:
    • Cancel
    • Confirm deletion

Step-by-Step #

  1. Open the task on the manage page.
  2. Go to the Details tab.
  3. Click Delete in the Delete Task card.
  4. Review the confirmation modal.
  5. Click Confirm deletion to complete deletion.

What Happens Next #

After successful deletion:

  • the task is removed from the task table
  • caches are refreshed
  • you are redirected to the Tasks list page
  • admin notice appears, e.g. Task #365 deleted successfully.

Bulk Deletion (Tasks List Page) #

Bulk deletion is available on the Tasks list page for controlled cleanup runs.

Step-by-Step #

  1. Open /wp-admin/admin.php?page=psfw-tasks.
  2. Select one or more tasks.
  3. Choose Delete in bulk actions.
  4. Apply bulk action.

What Happens Next #

After successful bulk delete:

  • selected tasks are deleted
  • list caches are refreshed
  • list context is preserved where possible (view/filter/search/sort)
  • success notice shows deleted count (for example: 3 tasks deleted successfully.)

Permissions and Access #

Deletion is capability-protected.

Required Access #

For single deletion, users need:

  • task-delete capability
  • access to that specific task

For bulk deletion, users need:

  • task-delete capability

If access is missing, delete controls are hidden or blocked.

Safety Features Built Into Deletion #

Deletion flow includes safeguards such as:

  • confirmation modal before final delete
  • nonce verification for secure submission
  • capability checks before executing delete

Benefit:

  • reduces accidental deletions and unauthorized task removal.
  1. Verify the task is genuinely unnecessary.
  2. Check if status/assignment update would be better than deletion.
  3. If deleting, complete deletion in one clear action.
  4. Confirm success notice.
  5. Continue cleanup or resume normal operations.

Common Mistakes and Better Practice #

Mistake: Deleting Real Delivery Tasks Too Early #

Better practice:

  • keep legitimate historical tasks and update their status/metadata instead.

Mistake: Bulk Deleting Without Filter Check #

Better practice:

  • verify current filters/search before applying bulk delete.

Mistake: Assuming Delete Failed Because Task List Changed #

Better practice:

  • check the success notice first; redirects can alter list context and ordering.

Troubleshooting #

I Don’t See the Delete Button on Task Details #

Likely cause:

  • missing delete capability for current user.

Delete Action Does Nothing #

Check:

  • you clicked Confirm deletion in the modal (not just Delete card button)
  • session/form security state is valid (reload page and retry)

Bulk Delete Option Is Missing #

Likely cause:

  • current role lacks task-delete capability.

I Deleted a Task and Got Redirected to Tasks Page #

This is expected behavior for successful single-task deletion.

Summary #

Deleting a task in Productized Services is a structured cleanup operation: clear intent, confirmation step, secure execution, and visible success feedback.

Use it for true invalid/duplicate records, and use status/assignment updates for meaningful delivery history.

What are your feelings

Updated on March 3, 2026