Cancel a service request when you want to stop processing it but keep its details. Delete a request only when its details can also be permanently removed. These instructions describe cancellation and deletion in the browser.
Choose the right action
- Cancelled keeps the request and its details. Its status cannot be changed back to Open or In progress.
- Completed means the request has been processed and triggers the processing of hours, costs and inventory associated with completion. See completing a service request.
- Deletion permanently removes the request. It is not a status change, and the request cannot be restored through the user interface.
Cancelling requires permission to edit the request. Permission only to mark the request as completed or add comments and attachments is not sufficient. Deletion requires separate permission to delete. If an action is missing, ask an administrator to check your permissions.
Open the service request in the browser
Open Manage tasks → Service requests → Service requests. In the simplified menu, the path is Manage tasks → Service requests. Select Table views → Default view on the page and find the correct request. Check its identifier, title and any linked Spot before making changes.
Cancel the request
You can cancel a request whose status is Open, In progress or On hold. The Status field is locked for completed, cancelled or forwarded requests: you cannot change these statuses to Cancelled or reopen the request.
- Open the request's edit window using the pencil icon in its table row.
- Check the request's tasks on the Tasks tab. Agree separately on what to do with unfinished tasks: cancelling the request does not complete or cancel them.
- Check for ongoing time entries on the Logged work hours tab. Cancellation does not stop timers. Save the correct end time for each entry separately; see correcting a time entry.
- Select Cancelled in the Status field on the Basic info tab.
- Click Save or Save and close at the bottom of the window. Correct any save errors and save again.
Cancellation does not require completion conditions to be met, such as completing all tasks or obtaining required signatures. Required additional information fields for the service request type are also not checked when cancelling an existing request as they are when completing it. Basic information checks, such as a Spot required by the request type, still apply.
Cancellation keeps existing entries and costs. It does not trigger the creation of completion costs or the processing of inventory products, and it does not set a completion time for the request.
Email notifications about cancellation may be sent according to the service request notification settings. The request's public response page can no longer be opened again. However, a response can still be submitted from a response page that was already open when the request was cancelled, so cancellation should not be relied on to prevent all responses.
Verify the result by finding the request in the table again. If necessary, remove the previous status filter or filter the Status column to show cancelled requests. Open the request and check its saved status, the statuses of related tasks and the end times of time entries.
Prepare for permanent deletion
These deletion instructions apply only to requests with no related tasks. Check the Tasks tab in the edit window to confirm that there are no tasks. If the view warns that you lack task permissions, ask an administrator to verify this. An empty list alone is not sufficient in that case. The deletion protection for requests containing tasks cannot be relied on.
In the same window, check the Logged work hours, Products and Work costs tabs, as well as the Traveling allowance tab, which appears when the work time feature is enabled. In particular, check which entries have generated a cost row and which travel allowance entries are personal. A time entry, product row and travel allowance entry are separate records from the work cost row generated from them.
Save any details, attachments, discussions, signatures and entries you need separately. Deletion removes the request's additional information values, attachments, comments, discussions with their responses and response attachments, and the request's own signature requests and signatures. Links between purchase orders and the request are also removed. This action does not delete a linked Spot, product or purchase order. The old public response link stops working because the related discussion is deleted.
Delete the request and choose what happens to its costs
Click the trash icon in the request's table row. The icon appears only if you have permission to delete.
Completed request
If the request is Completed, the confirmation window offers two deletion options:
- Permanently delete the service request and all related work costs deletes the request and its work cost rows. Deleting a cost row also deletes the time entry, request product row or travel allowance entry it refers to. A personal travel allowance entry is kept even if its corresponding cost row is deleted. Deleting another cost removes the cost row without a separate source entry.
- Do not delete related work costs, only permanently delete the service request keeps the cost rows and their source entries. This option does not keep the request's attachments, discussions or signatures. A retained cost may display the saved work name, but the deleted request can no longer be opened.
The Completed status does not guarantee that every entry has a cost row. Automatic cost creation depends on products and travel allowances and, for hours, on a positive number of hours and the billability settings of the users who recorded them. Deleting costs affects only the source entries referenced by cost rows that have been created. Entries without a cost row may therefore remain even after this option is used.
Cancel stops the deletion of a completed request. This button does not change the request's status to Cancelled.
Request in another status
For a request in any status other than Completed, the confirmation uses Yes and No buttons. Yes confirms permanent deletion; No stops it.
In this case, the request's time entries, product rows and non-personal travel allowance entries are deleted directly. Any ongoing time entry is also deleted. Personal travel allowance entries and existing work cost rows, such as manually added other costs, are kept. In this case, keeping a cost row does not mean its source entry is kept. The option to keep costs offered for completed requests is not available.
Deletion may remove time entries even if deleting them individually would otherwise be blocked, for example because they have been approved or processed. Make sure you have the time and cost information you need before confirming.
Deleting the request or its product rows does not return used products to inventory or reverse previous inventory transactions. Check and correct any necessary inventory changes separately. Deletion also does not mean that all previous history events are removed.
How do cancellation and deletion affect reports?
Reports use different data sources. Cancellation or deletion may also change the results for an earlier period when the report is retrieved again.
- Service request status and count reports: cancelled requests are excluded. Turnaround time also uses only requests with the Completed status.
- Processing delay, commenting delay and MTBF: cancellation does not generally exclude a request. Inclusion depends on the report period and filters, and on the saved processing start time, comments or, for MTBF, the Spot link.
- Service request recorded hours: finished time entries for a cancelled request may still be included based on the time falling within the selected period. A deleted request is excluded even if one of its time entries remains.
- Work costs and income: retained costs and income for a deleted request may remain in an administrator's ungrouped report for the period when the cost rows were created. Grouping by folder or Spot requires an existing request, so rows for a deleted request are excluded from these groups. Filters may also exclude rows.
- Product costs: a retained product cost may remain in an administrator's report by product if its source product row was also kept. A previous inventory transaction may still count towards product usage quantities even if the request and its cost were deleted.
Deletion removes the request from the data used by reports based on requests. Users other than administrators do not receive costs related to a deleted request in the data for work cost or product cost reports.
For detailed time bases and calculation rules, see service request report counts, delays and mean time between failures, interpreting work costs and income and product usage quantities and costs.
Check the effects of deletion
Refresh the service request list and confirm that the request can no longer be found by its identifier. Check for any error message: accepting the deletion confirmation alone does not prove that deletion succeeded.
If costs were kept, ask an administrator to check them under Manage tasks → Work costs. Select a period that includes the creation time of the cost rows. In particular, remove Spot, folder and service request type filters, since information based on the deleted request no longer matches them. Rows related to a deleted request do not appear in other users' cost searches.
The work name or euro amount of a retained cost does not show that the request or its source entry has been kept. Check entries and personal travel allowances separately in their own views. See viewing hours and costs. Retrieve the reports you want to compare again using the same period and filters, and interpret the changes based on the differences between data sources described above.
Cancelled requests on mobile
In Android's Service requests view, cancelled requests are viewed on the Cancelled tab. The corresponding view in iOS is titled Cancelled. Visibility still depends on the user's permissions.
On Android, the details of a cancelled request hide the actions for completion, editing additional information and the Spot, adding comments and tasks, and adding products, hours and travel allowances. Signature actions are also hidden. The work hours section remains visible.
On iOS, the information, attachment, purchase order, task and expense sections remain, but the timer and signature sections are omitted. Adding attachments is hidden for a cancelled request. Missing actions do not mean that the request or its entries have been deleted, and the absence of the timer section does not prove that an ongoing time entry has ended.