Issues
Track problems found on a project against your own issue schemas, discuss them, chart them, and exchange them with other tools as PDF, CSV or BCF.
An issue is a problem raised at a place in the model: a crack an inspector found on level 2, a clash between a duct and a beam, a question for the designer. Each issue has a number (#12), a title, the point in the model where it was raised with the camera view at that moment, and the model elements it is about. Everything else it records — status, priority, who is responsible, due date — comes from the project's issue schema, which you set up yourself.
You find issues under the project's Issues, with Charts and Schemas below it. The QR codes the AR app lines the models up with are not issues: they are markers, with a page of their own.
Who can do what
What you may do with issues comes from your permission profile on the project. Each area has its own level: No access, View, Create, Edit or Full control, and each level includes the ones before it. Organization owners and admins can do everything, whatever their profile. Issue schemas are different: they belong to the project's setup, so only people who manage the project can change them.
| Task | Who |
|---|---|
| See issues, their history, attachments and charts | Issues at View or above |
| Raise an issue (AR app or API), import issues from BCF | Issues at Create or above |
| Comment on an issue, edit or delete your own comments | Issues at Create or above |
| Edit an issue you raised, or one that names you or your company, and add or remove its files | Issues at Create or above |
| Edit anyone's issue and its files | Issues at Edit or above |
| Delete an issue, restore a deleted one, delete anyone's comment | Issues at Full control |
| Create, edit or delete issue schemas, fields and categories | Organization owners and admins, and project admins |
A profile can also be set to Own company only. Someone with that profile sees only the issues created by people in their own company, plus the issues that name them or their company in a person field. Their charts count only those issues. At Create they edit only their own among them: the ones they raised or that name them or their company.
Set up an issue schema
Every new project starts with one schema, "General", copied from the general template. It has the fields Status, Priority, Description, Assignee, Responsible, Due date and Tags, and the categories Defect (with Structural, MEP and Architectural inside it), Clash and Request for information. Its names are in the language of whoever created the project. It is your copy: rename or change it as you like.
The status field
Every schema has a Status field, whichever template it starts from. It starts with three statuses: Open, Pending and Closed. You can rename the field, and rename, recolour, reorder, remove and add statuses, for example to match the statuses of another tool. The field cannot be removed, and no other field can take its place.
Each status has a colour and says what it counts as, the same way the values of a progress status set do:
| Counts as | Means | To start with |
|---|---|---|
| Open | Waiting for someone to start on it, like a backlog. | Open |
| In progress | Someone is dealing with it. | Pending |
| Closed | Finished. The issue should not change any more. | Closed |
A new status counts by its place until you pick: the first as open, the last as closed, those between as in progress. The charts draw statuses in their colours.
A closed issue cannot be edited, apart from its status: its title, category, other fields and files stay as they are, and the AR app hides it in the model. To change something on it, reopen it first. Comments stay open on a closed issue. See Work on an issue.
Open Issues → Schemas, pick the schema and open its Status field.
Under Statuses, click a status's colour dot to change it, type to rename it, and use Move up and Move down to put the statuses in order. Choose Add status for a new one.
Under each status, choose what it counts as: Open, In progress or Closed.
Choose Save changes. Issues in a renamed status keep it under its new name. Issues in a removed status lose their status.
Open Issues → Schemas and choose New schema.
Give it a name that is unique in the project, for example "Site inspection". Under Start from, pick General template for the starter set of fields and categories, or Blank for none.
Choose Add field for each thing an issue should record. Pick a type: Text, Number, Yes / no, Date, Select, Multi-select, Tree select, Tree multi-select or Person. A select needs at least one option. A tree select holds nested options, and any option at any level can be picked. A person field can point at Project members, Companies or Members and companies, and can Allow multiple.
Choose Add category to build the category tree. On each category, tick the Required fields. A field required on a category is also required on every category inside it.
Some choices are fixed
A field's type, whether it allows multiple people, and who can be picked cannot be changed once the field exists. Labels and options can.
Find issues
The Issues page lists the project's issues with their category, schema, related objects, attachments, creator and dates. Click a column header to sort by number, title, created or updated date. The columns menu shows, hides and reorders columns, including one per schema field.
Type a title or a number in the search box. 12 and #12 both find issue 12.
Open Filters (or press F) to filter by Schema, category, creator, model, created dates, or Include deleted. A category filter includes every category inside it.
Pick a schema to filter by its own fields too: text contains, one of several options, a person, yes or no, or a range of numbers or dates.
Your filters and hidden columns are saved for you on each project, so the list looks the same next time. A link with filters in it opens with those filters, which is handy for sending someone "all open structural defects".
Raise an issue
There is no "New issue" button in the web app. An issue needs a point in the model and a camera view, so it is raised from a 3D view that has them — in practice the AR app on site — or through the API. The issue is numbered next in the project and recorded as raised by whoever was signed in.
When it is created, the values are checked against the schema. If the issue's category requires Status and Priority and they are missing, the issue is refused.
Work on an issue
Click a row to open the issue in a side sheet.
On Details, change the title, the category or any field. Fields marked * are required by the selected category.
Under Elements, see the model elements the issue is about and their properties, read from the model's current conversion. If an element was picked on an older version of the model, it says so.
Choose Open in viewer to open the model with the camera where the issue was raised.
Under Attachments, add photos, documents or other files, or remove them.
Choose Save changes.
The Activity tab shows every change to the issue: who changed what, from what, to what, including files added and removed.
Every issue also has a page of its own, at /projects/…/issues/12 for issue #12. Choose Open as page in the sheet to go there, or Copy link to send it to someone. The page shows the same details with the activity beside them, and the same actions in its header. Emails and notifications about an issue open this page.
Changing the category re-checks the whole issue. Moving an issue into a stricter category fails until you fill in what that category requires.
A closed issue, one whose status counts as closed, takes no change but its status. Its other fields and its files are greyed out, and the sheet says so. To edit it, set a status that counts as open or in progress, choose Save changes, then make your changes. Comments can still be added. Anyone who can edit the issue can reopen it.
Discuss an issue
Open the issue and go to Comments — a tab in the side sheet, a section under the details on the issue's page.
Write in the box. Type @ and the first letters of a name to mention someone on the project, then pick them from the list.
Choose Attach files to add photos or documents, up to 10 per comment.
Choose Comment, or press Ctrl + Enter (⌘ + Enter on a Mac).
Everyone you mention who can see the issue gets a notification, and an email on the project's schedule for "Mentioned in an issue comment". It opens the issue's page at your comment. People who cannot see the issue — someone limited to their own company's issues, for example — are not told.
You can edit your own comments and add or remove their files; an edited comment says so. You can delete your own comments, and people with Full control of issues can delete anyone's. The issue's Activity records every comment added, edited or deleted, with the start of its text. A deleted issue's comments can be read but not changed.
Delete an issue
Open the issue and choose Delete issue. The issue leaves the list, but it is not erased: tick Include deleted in the filters to see it again, read-only, with its history. The history records who deleted it.
For 30 days you can bring it back. In the list a deleted issue shows how many days it has left; open it and choose Restore issue. It comes back with its number, fields, files and history, and the history records who restored it. After 30 days it is deleted for good, with its files and its comments; its entries in the project's activity stay. An issue whose schema has been deleted since cannot be restored.
See issues in the 3D viewer
The viewer shows the project's located issues as pins, beside the placed markers. The Issues panel has the same filters as the list, plus Storey. Click a pin to open the issue. The viewer shows at most the newest 5,000 issues; narrow the filters to see the rest. Issues without a location have no pin. See Models for the viewer itself.
Charts
Issues → Charts is the project's issues board: a dashboard of widgets over the project's live issues. Everyone who may read the project's issues sees it; whoever manages the project can add charts, change them, resize, move and remove them. It offers the issue metrics only: Issues (as they stand now), Open issues, Issues created, Issues due (due dates still ahead included) and Issue completion, cut by status, assignee, creator and storey.
It starts with ten charts: issues by creator and by status, assignee by storey, creator by storey, issues created per day by assignee or creator over the last 90 days, issues due per week by assignee or creator, and storey by creator or by status. When there are many values, a chart shows the largest and puts the rest into Other. Statuses are drawn in their colours; a status with the same name in two schemas takes the colour of the schema created first. Statuses and storeys appear exactly as they were typed.
Status, assignee and due date come from the fields that have that role in each schema, whatever they are called, so you can rename them. The "General" schema starts with its Status, Assignee and Due date fields in those roles. To chart another field, open it under Schemas and turn on Use as the Status in the charts (or the Assignee, or the Due date): only a select field can be the status, a person field the assignee (the first person in it counts) and a date field the due date. One field per schema holds each role, so turning it on moves it from the field that had it. A schema with no field in a role shows Not set for it.
The charts are worked out when you open them, so a new issue shows straight away. Deleted issues are not counted, and issues without a due date are left out of the charts by due date.
Export issues as PDF
On the Issues page, select issues with the checkboxes and choose Export 3 as PDF, or choose Export PDF with nothing selected to export every live issue in the project — not only the filtered ones. One export takes up to 2,000 issues.
The PDF is made in the background: you get a notification and an email with the download link when it is ready, and the link lasts 7 days. See Exports.
The PDF has one issue per page, laid out like a form: schema, category, storey, creator, dates, every field, and its attachments. It is written in your language and your time zone.
Export issues as CSV
On the Issues page, choose Export CSV to export the list as you have it filtered and sorted — every page of it, not only the one on screen, and not the selection. Tick Include deleted first to have deleted issues in it too. Up to 50,000 issues at once.
The export runs in the background: you get a notification and an email when the file is ready, with a link to download it for a week. The file has one row per issue — number, title, schema, category, who created it, when it was created, updated and deleted, its model and storey — then one column per field, named as in your schema. People are written by name, choices by their label, dates as 2026-11-02. Column titles are in your language; what people typed is left as it is. It opens in Excel with accents intact.
Export issues as BCF
BCF is the format coordination tools such as BIMcollab, Solibri and Revit plug-ins exchange issues in. On the Issues page, choose Export BCF, then BCF 3.0 or BCF 2.1 — 3.0 unless the other tool only reads 2.1. With issues selected, the file holds those; with none, the list as you have it filtered. Up to 2,000 issues at once. Like the other exports it runs in the background and arrives in your notifications.
Each issue becomes a topic with its title, category (as the type), status, priority, labels (your Tags field), description, assignee and creator (by email), due date and comments, plus one viewpoint: the camera where the issue was raised, its model elements, and its first image as the snapshot.
Import issues from BCF
On the Issues page, choose Import BCF.
Choose a .bcf or .bcfzip file (BCF 2.1 or 3.0, up to 100 MB) and the schema new issues go into.
Choose Import. The import runs in the background; you get a notification and an email when it is done.
A topic that is already one of the project's issues — because it was exported from here, or imported before — updates that issue; the others become new issues. Importing the same file twice changes nothing the second time. Status, priority, labels and type are matched by name to your schema's options and categories, and people by email to the project's members. What does not match is left out, and the email lists it: an unknown status, a label your schema does not have, someone not on the project. A comment by someone not on the project is kept under your name, with theirs beside it. New issues take the topic's camera, the model elements it selects, and its snapshot as a file.
You need Issues at Create or above to import, and at Edit or above to update issues that are already there; without it those topics are skipped.
Good to know
- Emails and notifications. When an issue names a project member in a person field — on creation or on a later edit — that person gets a notification under the bell and an email, "You were added as Assignee on issue #12", with an Open issue button that opens the issue's page. You are not told about your own change. Companies are not notified. If someone is taken off the issue before a queued email goes out, it is withdrawn.
- Email timing is set per project by its admins in the project's notification settings: Instantly, Hourly, Daily, Weekly or Never for "Issue created or assigned to you" and for "Mentioned in an issue comment". Digests go out in each person's own time zone if they have set one.
- Files can be up to 25 MB, or 50 MB for a PDF.
- Deleting a schema is refused while live issues use it. A schema used only by deleted issues is kept in the background so those issues keep their labels, and its name stays taken.
- Deleting a category works only when it has no categories inside it and no issues filed under it, deleted ones included.
- Deleting a field removes it from every category that required it. Issues lose what they recorded in it.
- Renaming an option in a select or multi-select keeps it on the issues that hold it, under its new name. Edit its line in Options rather than deleting it and adding another: an option that disappears while another appears in its place counts as renamed.
- Removing an option removes it from the issues that hold it. A multi-select keeps their other choices.
- API keys can read or write issues with the
issuescope. See the API reference for issues, issue comments and issue schemas.