Issues

What is an issue

An issue is a trackable problem, task, or question related to your assets, processes, or project work. Issues help your team capture what needs attention, assign it to a person or a group, and move it through a defined status flow until it is resolved.

Think of an issue as a single, well-scoped item you can discuss, update, and close when done.

Issues page overview and layout

The Issues page (Issues in the sidebar) is your main hub to view, filter, create, and update issues. You need the issues.read permission to see it.

At the top is the New Issue button (needs issues.create — all built-in roles have it). Below is the Issues table: sortable column headers, a filter row directly under the headers, one row per issue, and pagination controls at the bottom.

If your project has not configured its issue statuses yet, a hint banner suggests setting defaults.

Issues table columns

Each row represents one issue. The columns are:

• Status bar: a small colored bar for a quick visual status.
• Id: the issue number for quick reference.
• Title: the short name of the issue.
• Priority: how urgent or important the issue is (levels defined by your project).
• Assignee: the responsible party — this can be a single user OR a group.
• Type: the category of the issue (defined by your project).
• Status: the current status label in words.
• Due date: the date the issue should be closed by, shown in red with an Overdue chip when it has passed and the issue is still open. You can sort by it, but it has no filter box.
• Created By: the user who created the issue.
• Location: where the issue is, as a path in the project's location tree.
• Actions: a delete icon. The delete column only appears if you hold the issues.delete permission (Project Admins by default).

Filter issues — filters live in the URL and are shareable

Use the filter row directly under the column headers to narrow results: by title or Id, type, priority, status, assignee, creator, or location. Filters can be combined.

Your filters are stored in the page URL, so they survive a refresh — and you can copy the address bar and send the link to a teammate to share the exact same filtered view.

Sort, resize, and paginate the issues list

Click a column header to sort by that column; click again to switch between ascending and descending. Drag the right edge of a column header to resize it.

Use the pagination controls at the bottom of the table to move between pages or change how many rows are shown at once. If you cannot find an issue, check your filters and pagination first.

How to create an issue

Step-by-step:

1. Click New Issue (needs issues.create — all built-in roles have it).
2. Enter a clear Title (required), for example "UPS inverter overtemperature".
3. Add a Description with context, symptoms, or expected behavior.
4. Choose a Priority and a Type (both lists are defined by your project).
5. Assign the issue to a user or a group (optional but recommended).
6. Link Assets if the issue is tied to specific equipment.
7. Pick a Location if you want to record where the issue is (optional).
8. Click Create.

After creation, the issue appears in the list and can be opened for further updates. Tip: links that end in ?create=1 (for example from the Home setup checklist) open this dialog automatically.

Open and edit an issue

Click anywhere on an issue's row to open the issue dialog. There you can edit the title and description inline, change priority, type, assignee, due date, location, and status, manage linked assets, attachments, and linked planner activities, and add comments.

Changes save field-by-field, so you can update one item at a time; every change is recorded in the issue history.

Edit title, description, priority, and type

In the issue dialog:

• Title: keep it short and specific so issues are easy to scan.
• Description: add steps, impact, context, or links.
• Priority: adjust urgency as work progresses — raise it if the issue blocks work, lower it when it is no longer urgent.
• Type: reclassify the issue if new information appears; this keeps reporting accurate.

Priority and type options are defined by your project. If an option you need is missing, ask a project admin to update the project's configuration sets.

Assign an issue to a user or a group

Use the Assigned To field to pick who owns the issue. You can assign either a single user or an entire group (groups are defined by project admins on the project's Groups page).

Assigning to a group means every member of that group is treated as responsible — any group member can edit the issue and change its status, and group members are notified. When you change the assignee, the update is recorded in the issue history.

Due dates and the Overdue chip

Every issue can have a due date — the date by which it should be fixed and closed. Set it when you create the issue, or change or clear it later from the Due date field in the issue dialog. Every change is recorded in the issue history.

When the due date passes and the issue is still open, the list shows the date in red with an Overdue chip, and the issue dialog shows the same chip next to the date. Sort the list by the Due date column to chase the most urgent issues first. Closed issues are never shown as overdue.

The assignee (or the creator, when the issue is unassigned) receives an Issue overdue notification the day the issue slips — once per slip, so moving the date or changing the status re-arms it. You can tune the channels for it in Settings → Notifications. The assistant can set or clear due dates too: ask it to "set issue 45 due next Friday", or to list overdue issues.

Set where an issue is — the Location field

Every issue can have a Location: a place from the project's location tree (site, building, floor, room and so on). It tells the team where to go, and lets you filter and sort issues by place.

When you create an issue:

1. Click New Issue and fill in the title and the other fields.
2. Click the Location field ("Select location (optional)").
3. Pick a place from the tree, then click Create.

On an existing issue:

1. Click the issue's row to open the issue dialog.
2. Click the Location field and pick a place, or pick — No location to clear it.
3. The change saves at once and is recorded in the issue history.

Good to know:

• The Location column in the Issues table shows the full path. You can sort by it and filter on it.
• The location is separate from linked assets. Linking an asset does not fill in the issue's location, so set it yourself if you want it.
• The places come from the project's location tree. If a place is missing, ask someone who can edit locations to add it. A location that still has issues assigned to it cannot be deleted.
• Changing the location follows the same rules as editing the issue.

Coming from the Map: when you select a location or an asset on the Map and click View all issues, the Issues page opens showing only that pin's issues. A chip above the table says so, for example "Issues located at Main Building" or "Issues linked to UPS-001". Click the x on the chip to show all issues again. The narrowed view survives a page refresh.

Update issue status and allowed transitions

Use the Status control in the issue dialog to move the issue through your project's status flow (for example Open → In Progress → Closed, though your project can use different names).

The project's transition policy decides which statuses can follow the current one, so some options may be disabled from where you are now. Changing status needs issues.status.update (Project Admins and Members by default) — or you qualify automatically if you created the issue, are its assignee, or belong to its assigned group.

When you save a new status, the change is added to the history timeline.

Who can edit an issue — permissions and bypass rules

You can edit an issue and change its status if any of these is true:

• You created the issue.
• You are the issue's assignee.
• You belong to the group the issue is assigned to.
• You hold the issues.update permission (for edits) or issues.status.update (for status changes).

In other words, creators, assignees, and assigned-group members can always work on their own issues, even without the permissions. The project owner can always do everything. If a control is disabled for you and none of the above applies, ask a project admin to adjust your role.

Link assets to an issue

Use Linked Assets to connect related assets to the issue, so everyone can see which equipment is affected. You can select multiple assets, and remove links later — additions and removals are recorded in the issue history.

Linked assets also make the issue visible from each asset's side.

Issue attachments

The Attachments section of the issue dialog lets you attach files to the issue itself. You can upload new files or pick existing documents already stored in the project's Documentation.

Use attachments for photos of the problem, reports, or any evidence that belongs with the issue. You can also attach images or PDFs directly to individual comments when posting them.

Linked planner activities on an issue

The issue dialog includes a Linked planner activities card listing schedule activities connected to this issue. This keeps the plan and the problem in one place — click an activity to jump to it in the Planner.

Seeing the list needs planner.read; adding or changing links needs planner.update.

Add comments to an issue

At the bottom of the issue dialog you can add comments to keep discussion and evidence together.

How to add a comment:

1. Write your message in the comment box.
2. Optionally attach images or PDF files.
3. Click Comment.

Commenting needs the issues.comment permission — all built-in roles (Project Admin, Member, Technician) have it by default. Comments appear in the issue history; a comment needs text or at least one attachment to post.

Issue history timeline and filters

The History section shows a timeline of everything that happened to the issue: status updates, field edits, assignee and group changes, linked-asset changes, comments, and system entries.

Use the filter dropdown to focus on one category:

• All
• Field changes
• Comments
• Status changes
• User (assignee) changes
• Group changes
• Linked assets
• System

This helps you quickly understand what changed and when.

Issue deep links from notifications and emails

Notifications and emails about issues (for example "issue assigned" or "new comment") link straight to the issue: the link opens the Issues page with the right issue dialog already open.

You can produce the same effect yourself — a link to the Issues page with ?issue=<id> at the end opens that issue directly. This makes it easy to point a teammate at one specific issue.

Export the issues list to Excel

You can download the Issues table as an Excel file (.xlsx) — handy for a punch list you need to send to someone.

1. On the Issues page, set the filters and sorting you want. The export matches what the table shows, including a view narrowed from the Map.
2. Click the three-dot Page actions button next to the Issues title and choose Export….
3. The Export table dialog opens. If you have filters on, it reminds you that the active filters and sorting apply to the export.
4. Optional: switch on Only visible to me to keep the file private.
5. Click Export. The button shows that the file is being generated. When it is ready, the file opens in a new browser tab and a message confirms the export.

What is in the file: one row per issue with its Id, title, priority, assignee, type, status, location, due date, who created it and when, and the description. All matching issues are exported, not just the current page, up to 5,000 rows.

Where the file goes: without the switch, the message reads "Export ready — saved to the project's documents". With Only visible to me on, it reads "Export ready — saved privately for you" and only you can see the saved file.

Anyone who can see the Issues page (issues.read) can export — no extra permission is needed.

Delete an issue

Click the delete icon in the Actions column to remove an issue. You will be asked to confirm because deletion cannot be undone.

Deleting needs the issues.delete permission — Project Admins by default. If you do not see a delete column at all, you do not hold this permission.

Issues troubleshooting and FAQ

Q: Why can't I change the status? A: Either the transition policy does not allow that status from the current one, or you lack issues.status.update and are not the creator, assignee, or an assigned-group member.

Q: Why can't I edit the issue? A: Editing needs issues.update — unless you created it, are assigned to it, or belong to its assigned group.

Q: Why don't I see a Type or Priority option I need? A: Those lists are defined per project. Ask a project admin to update them in Project Settings.

Q: Why did my issue disappear from the list? A: Check the filter row and pagination first — remember filters persist in the URL. If you came from the Map, a chip above the table may be narrowing the list to one location or asset — click the x on it to show all issues. The issue may also have been deleted.

Q: Can I attach files? A: Yes — to the issue itself via the Attachments section (upload or pick existing documents), and images/PDFs directly on comments.