Issues

What is an issue

An issue is a trackable problem, task, or question related to your project assets or work. Each issue has a title, description, status, priority, type, and optional assignee. Issues help your team capture what needs attention, route it to the right person, and track progress until it is resolved.

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

Opening the Issues screen

To reach the Issues screen:

1. Tap the hamburger menu icon (☰) to open the side drawer.
2. Tap Issues in the module list.

The screen shows all issues for your active project, with a badge in the header showing the total count.

Issues list layout

The Issues screen shows:

• A floating glass header with the Issues title, the total issue count, and a + button to create a new issue.
• A search bar and a Filters button, with removable chips for any active filters.
• A scrollable list of issue cards, each showing the status colour, title, status label, priority, type, and assignee.

When you scroll down, the search and filter row tucks away automatically to give the list more room — scroll back up to bring it back. A loading indicator appears at the bottom while more issues load.

Search issues

Tap the search bar at the top of the Issues screen and start typing. Results update automatically after a short pause (about a third of a second) — there is no separate search button.

To clear the search, tap the X inside the search bar or delete all text. Search and filters can be combined.

Filter and sort issues

To narrow or reorder the issue list:

1. Tap the Filters button next to the search bar.
2. A filter sheet slides up from the bottom.
3. Select values for Status, Priority, Type, Assigned to, or Created by — all are multi-select.
4. Choose a sort option in the same sheet to change the list order.
5. Apply to see the results.

Active filters appear as chips below the search bar. Tap the × on a chip to remove that filter individually.

Pull to refresh and infinite scroll

Drag down from the top of the issue list and release to refresh — this reloads issues from the server to pick up changes made by teammates.

The list loads 25 issues at a time. As you scroll near the bottom, the next page loads automatically with a small loading indicator.

Create a new issue

Step-by-step:

1. Tap the + button in the Issues screen header.
2. A Create Issue sheet slides up.
3. Fill in the Title (required) — keep it short and specific, for example 'UPS inverter overtemperature'.
4. Add a Description with context, symptoms, or expected behaviour.
5. Select a Priority and a Type from your project's configured options.
6. Optionally assign the issue using the assignee picker.
7. Optionally tap the Location row and pick where the problem is from your project's location tree.
8. Tap Create.

The issue appears in the list immediately after creation.

Create issue field guidance

Title: Required. Keep it brief and specific. Avoid vague names like 'Problem' — use 'Cooling fan failure in Rack B3' instead. Description: Optional but strongly recommended. Add symptoms, steps to reproduce, or background context. Priority: Choose based on urgency or risk. Use a higher priority for safety or production-blocking issues. Type: Pick the category that best fits. Types are configured per project. Assignee: Select the team member responsible. Unassigned issues can be harder to track. Location: Optional. Pick the site, building, room or other place from the project's location tree, so the team knows where to go. It reads "Select location (optional)" until you choose one.

Open and view an issue

Tap any issue card in the list to open the issue detail sheet. It slides up from the bottom and opens in read-only mode first, showing all fields, the attachments, the comments, and the history feed.

Scroll within the sheet to see everything; swipe it down to close.

You can also land directly on an issue by tapping an issue notification (in the app's Notifications inbox or a push notification) — the app opens the Issues screen with that issue's sheet already open.

Edit issue title and description

In the issue detail sheet, tap the Title or Description to open its inline editor. You can edit both fields and then confirm them together with a single Save — changes are not sent until you save.

Saved changes are recorded in the issue history feed so your team can see what was updated and when.

Change status, priority, type, or assignee

In the issue detail sheet, tap the Status, Priority, Type, or Assignee field. A compact picker slides up inside the sheet — choose a value and it is applied.

Statuses, priorities, and types are defined by your project (a typical status flow might look like Open → In Progress → Resolved → Closed, but your project may use different names). Every change is recorded in the issue history feed.

Assigning ensures someone is accountable; to reassign, simply tap the Assignee field again and pick a different member.

Set a due date

Every issue can carry a due date — the date it should be fixed by. When creating an issue, tap the Due date row to open the calendar and pick a day; leave it empty for no deadline. In the issue detail sheet, tap the Due date field to change it, or use Clear in the calendar to remove it.

When the date passes and the issue is still open, the field turns red with an Overdue marker, and the issue row in the list shows a small clock icon. Use the "Due date — soonest first" sort to see what is due next. Closed issues are never shown as overdue.

The assignee (or the creator, when unassigned) gets an Issue overdue notification the day it slips; tapping it opens the issue. Tune the channels in Settings → Notifications.

How to set an issue's location and show it on the map

Every issue can carry a location — a place from your project's location tree, such as a site, building, floor or room.

How to set or change it:

1. When creating an issue, tap the Location row. In an existing issue, open it and tap the Location field.
2. The Select location picker slides up inside the sheet. Browse the tree, or type in the search box to find a place by name, code or path.
3. Tap a location. In an existing issue the change is saved straight away. Tap "— No location" to clear it.

The field shows the full path, for example Site A > Building 2 > Room 104. If the picker says "No locations configured for this project.", a project admin has to set up the locations on the web app first.

Show on map: when the Map module is on for the project, an open issue can show a Show on map row under its fields. It appears when the issue's location, or a place above it in the tree, has a pin on the map. If not, it uses the first linked asset that has a pin. Tap the row to open the Map on that pin. When there is no pin to land on, the row is not shown. See the Map help for what you can do from there.

Add attachments to an issue

The issue detail sheet has an attachments area where you can attach evidence to the issue:

1. Tap the add-attachment control.
2. Choose the source: take a photo with the camera, pick from your photo library, or pick a file.
3. The attachment uploads and appears in the strip.

Tap an attachment to preview it, or use its remove control to delete it from the issue.

Add a comment to an issue

Comments live in the issue detail sheet:

1. Scroll to the comment area.
2. Tap the comment input and type your message.
3. Send it.

Comments appear in the issue's history feed alongside other changes, and relevant team members are notified. Commenting is covered by the issues.comment permission, which all built-in roles have by default.

Issue history feed

The history feed in the issue detail sheet shows a timeline of everything that happened on the issue: status changes, field edits, assignee changes, and comments — each with who did it and when.

Use the history filters to focus on one kind of entry: All, Comments, Status, Assignee, or Fields.

Delete an issue

To delete an issue:

1. Open the issue detail sheet.
2. Tap the Delete action.
3. Confirm in the prompt — deletion cannot be undone.

Deleting issues requires the issues.delete permission, held by Project Admins by default. If the server rejects the deletion, your role does not include it — ask a project admin.

Opening an issue from a notification

When you are notified about an issue — for example when it is assigned to you or someone comments on it — tapping the notification takes you straight to it:

• Tapping a row in the Notifications inbox opens the Issues screen with that issue's detail sheet already open.
• Tapping a push notification does the same, even when the app was fully closed.

If the issue belongs to a different project than your active one, the app switches projects first, then opens the issue.

Who can edit issues — how permissions work

On mobile, the issue editing controls are always shown — the server checks your permissions when you save. If a change is rejected, your project role does not allow it.

How issue permissions work:

• Viewing, creating, updating, and commenting (issues.read, issues.create, issues.update, issues.comment) are granted to all built-in roles by default.
• Changing status (issues.status.update) is granted to Project Admins and Members by default.
• Deleting (issues.delete) is Project Admin only by default.

Regardless of role, the issue's creator, its assignee, and members of an assigned group can always edit the issue and change its status. The project owner can always do everything. If an action keeps failing, ask a project admin to adjust your role.

No project — empty state

If you have not joined any project yet, the Issues screen shows a "No project joined yet" state with a "Join with invite code" button. Tap it to enter an 8-character invite code and join a project. Until you join one, the drawer shows only Chat and Documents.

If you switched to My Workspace, the screen says "You're in My Workspace" instead, with a Select project button that opens the drawer so you can switch back to a project.

If you are waiting to be added, ask a project admin to send you an invite code.