The Dashboard’s Changelog helps you track the creation and status changes of tasks and service requests, as well as the recording of new messages. You can check who performed an action and open any record that still exists to view it.
Open the Changelog
Sign in to the Spotilla browser application and select Dashboard → Dashboard from the menu on the left. Find the Changelog panel on the page. If the panel is missing, see managing Dashboard panels and layout.
You need access to the browser application. For a Manager user, the log only includes current tasks, service requests and messages that they have permission to access. Displaying the panel does not grant any additional permissions.
What does the Changelog include?
- Tasks: creation events and events in which a task’s status changes.
- Service requests: creation events and events in which a service request’s status changes.
- Messages: creation events for new messages.
The log does not show changes to Spots or edits that only affect other fields, such as changing a task’s name. Later edits to a message are also excluded from this event stream. The Changelog is not a complete history of all changes or deletions.
When you need the previous and new values of changed fields or a more extensive history, see finding change history. A Spot’s Read Events on Android and iOS cover different data: they are not a mobile version of this Changelog. See the separate articles on Spot Read Events and troubleshooting integration errors using the log.
Read an event row correctly
Events are listed from newest to oldest. Events recorded today show the time; older events show the date. The time is based on the service’s time zone. Scroll down within the panel to see older events; they are loaded in batches of 20. The panel does not have its own date range selector.
The row shows who performed the action, the event and the target. created means that a new record was created. A status change shows Status → followed by the status after the event. A task moving to completed status is shown with the word completed. The status shown in the row describes that event; the target’s current status may already be different.
The target’s name and the user account’s name are retrieved from current records. An old event may therefore appear with a name that was changed later. For a service request creation event, the sender’s name saved with the request may be shown as the person who performed the action.
Deleted user means that no display name was found for the saved user identifier. This text alone does not prove that the user account was deleted. System change is shown when both the name and identifier of the person who performed the action are missing.
Open an existing task, service request or message by clicking its bold name in the event row. The record that opens is the current record, not a snapshot from the time of the event. Opening it does not restore previous values or change any data.
Filter events
Open the search row using the magnifying glass icon at the right edge of the panel header. The same icon hides the search row; hiding it does not clear the search criteria.
- Choose target: select Service requests, Tasks or Messages. An empty selection shows all three categories.
- Search by targets name: search the task’s current title, the service request’s current title or the message’s current text.
- Search by spot name: limit events to targets currently associated with the Spot you search for.
- Search by users name: search for the person who performed the action using their current user account name. This does not search the freely entered sender name saved with a service request.
- Search by folder name: open the folder selector and select one or more folders. The selected folders and their subfolders are included through the Spots that currently belong to them.
Name searches match part of the text and are case-insensitive. Different search criteria are combined: an event must meet all active filters. If several folders are selected, belonging to any one of them or their subfolders is sufficient. Spot and folder filters exclude targets that do not have a matching current Spot association.
The search updates when a selection or search text changes. A change restarts loading the results from the newest events.
How does a deleted target affect the results?
An administrator can see an old event even if its target was later deleted, provided no filters based on the target’s name, Spot or folder are applied. If the target can no longer be found, the row uses the name saved in the history, if available, and shows target has been deleted. In this case, the target’s name cannot be opened as a link.
The deletion notice indicates that the target is missing now. It does not mean that this particular old event was a deletion event.
Target name, Spot and folder filters are based on current targets. An old event for a deleted target may therefore disappear from the search results even if it appears without these filters. A Manager user’s access restrictions are also based on current targets, so events for deleted targets are excluded for them even without search criteria.
Check for the latest information and a missing event
The Changelog does not update automatically along with the Dashboard’s task and service request lists. Reload the browser page when you want to check the latest saved events.
- Open the search row and clear the name searches and folder selections. Select the correct category or leave the category selection empty.
- Reload the page and apply the necessary filters again.
- Scroll down within the panel if you are looking for an older event.
- Check whether the event is included in the log and whether you have permission to access the current target. Editing only another field or editing a message does not produce a row in this log.
- Open the bold target name in the row you found and compare the event information with the current state. Use the change history if you need more detailed information about the changes.
A missing search result alone does not prove that a change was not made. It may be due to the scope of the log, a search criterion, access permissions or the target having been deleted later.