Skip to main content

Completed, Closed and deleted requests

When to use Completed, Closed or Delete, how each one behaves in lists, reviews and comment locking, and how to restore a deleted request.

Written by Gabriel Lecointere

Use case: A request is done, or it is not going anywhere, and you want it out of your active work without losing its history. ManyRequests gives you two "finished" statuses, Completed and Closed, plus deleting for requests you do not want to keep.

The short version

  • Use Completed when the work was delivered. This is the only status that asks the client for a review.

  • Use Closed to archive a request that was not delivered: cancelled, paused or put on the back burner.

  • Delete a request only when it should not be there at all, such as a duplicate or a test. You can still restore it later.

In request lists, Completed and Closed requests behave the same way: both leave the Open tab, and both show up together under Completed (admins) or Closed (team members and clients).

Completed

Closed

Deleted

Shown in the Open tab

No

No

No

Shown in the Completed / Closed tab

Yes

Yes

No

Counts toward the service's Max concurrent requests

No

No

No

Client is asked for a review (when Request reviews is on)

Yes

No

No

Comments locked (when Disable comments on completed requests is on)

Yes

Yes

n/a

How to bring it back

Change the status

Change the status

Restore it

Choose which statuses count as Completed and Closed

  1. Go to Settings > Modules and extensions > Requests.

  2. Pick a status under Completed status and another under Closed status.

    Completed status and Closed status fields in the Requests settings
  3. Click Save changes.

Each one must be a different status. You can rename them or pick any of your custom statuses (see How to create custom project statuses).

Mark a request as Completed

Your team: open the request and pick Completed in the Status dropdown on the right, or use Mark as complete in the three-dot menu.

Your clients: clients click Mark as completed at the top of the request.

Mark as completed button on a request, seen by a client

If Request reviews is turned on, the client is asked to Leave a review. Submit saves the review and completes the request, Skip completes it without a review, and Cancel leaves it open. When your team completes the request, the client can still leave a review from the request's activity.

Leave a review window with stars, Cancel, Skip and Submit

Close (archive) a request

There is no separate Archive button: closing a request is how you archive it.

  1. Open the request.

  2. Click the Status dropdown on the right.

  3. Select Closed.

    Status dropdown on a request with the Closed status highlighted

The request keeps all its comments, files and time entries. To reopen it, pick another status.

Find your finished requests

Go to Requests. Admins open the Completed tab; team members and clients see the same list under Closed. Both statuses appear in that tab.

Request list tabs with the Completed tab highlighted

Delete and restore requests

To delete a request, open it and choose Delete in the three-dot menu. You need the permission to delete requests.

Deleted requests are not shown in your lists, but they can be restored:

  1. Go to Requests and use the List view.

  2. Click Filters and turn on Include only deleted requests.

    Filters panel with the Include only deleted requests switch highlighted
  3. Select the requests you want back and click Restore.

Tips

  • Stop replies on finished work: turn on Disable comments on completed requests to lock comments on both Completed and Closed requests. See How to lock comments on completed requests.

  • Free up a slot: completing or closing a request frees a slot when the service limits concurrent requests, so the next queued request can start (see How to use Queue).

Related articles

Did this answer your question?