AssetBolt
AssetBolt
Docs
  • Docs
  • Changelog
  • Feature requests
  • Support portal
    • Checking assets in and out
    • Accessories, components, and consumables
    • Depreciation
    • Licenses and seats
    • Auditing assets
    • Devices
    • Digital assets
    • Asset requests
    • Action items
    • Reports and exporting data

Action items

Action items let your team track work related to assets and data in one place. You can create items manually, assign them, change their status, snooze them until later, and link them to an external ticket.

Overview

  • Create action items for follow ups like replacing a device, verifying inventory, or reviewing an integration alert.

  • Each item has a title, optional description, priority, assignee, due date, and status.

  • You can search items by title, description, assignee name, and linked resource name.

Creating and editing

  • Title is required. Maximum 200 characters. Description is optional. Maximum 5000 characters.

  • You can set or change priority, assignee, and due date at any time.

  • Assignees must be current members of your organization. The assignee list shows member names, falling back to email when a name is missing.

Statuses and lifecycle

  • Statuses: Open, In progress, Snoozed, Resolved.

  • Marking an item Resolved records the resolution time automatically.

  • Reopening an item to Open or In progress clears any resolution time and removes any snooze.

  • Snoozed keeps its wake up time. Use the Snooze action to set a future time, then the item will reappear when it is due. You cannot set Snoozed by changing status alone and you cannot snooze a resolved item.

Bulk updates

  • You can update the status of many items at once. If any selected item cannot be updated, none of the changes are applied.

Filtering, counts, and search

  • Filter by status, assignee, source, and related resource.

  • The status counts can be filtered to a specific assignee.

  • Results are ordered by newest first with stable pagination.

Linking to a ticketing system

  • You can push an action item to a connected ticketing provider like Linear or Jira. This requires a ticketing integration.

  • Only one external ticket can be linked to an action item. If one already exists, you cannot create another.

  • When a ticket is created from an action item, AssetBolt coordinates the request to avoid duplicates, even if multiple users try at once.

  • If a linked ticket is deleted in Linear, the link is cleared on the next sync.

  • You can also create a Linear issue for a specific device from an action item when Linear is connected.

Permissions

  • Viewing and assigning action items requires the ability to view action items.

  • Creating, updating, pushing to ticketing, and creating tickets for devices require permission to manage action items.

  • Pushing to a ticketing provider also requires the ticketing integration to be connected and enabled.

PrevAsset requests
NextReports and exporting data
Was this helpful?