The issue id should be shown in the issue pin in the files and sheets in the web and mobile version.  This feature allows to be found issues more quickly on the sheets. Show More

This option improves the issues recording on the construction site, as frequently used companies/persons/roles can be found more quickly to assigne the issues.  Show More

  The length of this view is fixed; sometimes it is difficult to see the data.     Show More

We would like more functions for the Thumbnail icon on Issues. We want to be able to reposition the section line which currently is not possible, once you select the Section analysis tool it snaps out of the edit issue mode so the section line cannot be changed, so if the design around an element has moved (which was visible in the issue thumbnail but has since moved 'out of frame' we cannot move the section line to suit, we would need to delete the issue, adjust the section plane and place it again, which makes managing issues more difficult.   The thumbnail is the first thing users see, and should have options to represent the issue in the best way possible. This would bring consistency and give more visual clarity of the issue. We would also like to be able to add a thumbnail for all issues, including those not created from within the model space. Even within the model space some issue are best represented as an uploaded file, not a screenshot from the model.  The current workaround is to attach the desired thumbnail image as an attachment, but it's not instantly visible and is often missed, therefore we'd like to propose this improvement of the Thumbnail.   Thanks! Show More

Currently, issues in ACC are often tied to specific elements or models (e.g., individual Revit objects, IFC, NWC files, or published views). This limits flexibility, especially when collaborating across multiple platforms such as Revit, Navisworks, and different ACC views. Challenges Issues are anchored to specific elements or files, making cross-platform collaboration and tracking more difficult. Revit modelers spend extra time locating and addressing issues that are tied to elements or views outside their immediate scope. Suggested Solution Enable Issues to Be Placed Anywhere: Allow users to create issues independently of specific elements or hosts, so they can be opened and reviewed in any context (Revit, Navisworks, multiple ACC views). Temporary Element Creation in Revit: When opening an issue in Revit, automatically generate a temporary marker or element at the issue location. This marker could be cropped to highlight the relevant area, providing clear context without tying the issue to a permanent model element. Benefits Improved Flexibility: Issues can be accessed and managed across platforms and views, regardless of their original creation point. Faster Issue Resolution: Revit modelers can quickly locate and address issues using temporary elements, streamlining their workflow. Better Collaboration: Teams can track and resolve issues more efficiently, without being restricted by model boundaries or file types. Implementing this feature would significantly improve issue management and speed up processing for large, multi-disciplinary projects. Show More

I’ve noticed a challenge when creating issues on ACC views that incorporate models from published Revit views. Currently, the issue references the original Revit file, not the specific ACC view where the issue was created. Context Our project—a large train station—uses very big Revit models that are slow to load in the ACC viewer. To address this, we rely heavily on coordination spaces and ACC views for efficient navigation and issue resolution. However, once an issue is created, it’s not possible to trace back to the specific ACC view used at the time. Current Workaround We can add a custom “URL” field to manually input the ACC view reference, but this is an extra step and prone to user error. Suggested Enhancement Automatically capture and store the ACC view reference (URL) when an issue is created. This would ensure every issue is directly linked to the exact view context, improving traceability and collaboration. Benefits Saves time: Removes the need for manual entry. Increases accuracy: Reduces the risk of incorrect references. Enhances collaboration: Team members can quickly jump to the relevant view for any issue, streamlining the review and resolution process. This improvement would greatly enhance our workflow and support more effective issue management on large, complex projects. Show More

Hi R&D team, We are facing huge amount of Snaglist issues from our Consultant and Client. We created a template report for exporting the Snaglists under issues that were issued by Client/Consultant to us which we assigned to our Subbies. We have come to know that there's a size limit of issues that can be exported in the report in PDF format as per ACC tech support answer to our query "Reports tool is 500 issues per report, up to 2,500 total".  I would like to request you increase the threshold limit please so we can generate all the assigned issues as per subbies.  Regards,  Oliver Jomadiao  Show More

Add a Kanban view for issues that allows you to sort them by various categories (ie. Company, Team Member, Status, etc.) Show More

I want to be able to download the NWD, which is already available on BIM360, but with markups, like with the PDFs how we can export the PDFs along with markups, I want to do the exact same thing but with NWD Can we take this as a feature request ASAP, since this would be really helpful for my current workflow, I am open to having a discussion on a teams call if required Show More

Hello, I noticed that when I create issues report, it shows its sheet placement location on a zoomed-in sheet inside the report. I think it would be a really good and cool idea to have this feature available for assets as well. Thank you Show More

Currently in the Issues tab within Build, sorting is limited to certain columns (Title, ID, Status, Type, etc.), but it is not possible to sort by “Assigned To” or “Created By.” This creates challenges when I need to quickly review issues grouped by assignee, since filtering only allows me to see one person’s issues at a time and doesn’t provide the bigger picture across the team. Having the ability to sort by “Assigned To” (and ideally “Created By”) directly in the Issues tab would make it much faster to review issue ownership and provide clearer visibility into workload distribution without having to rely on the filter function. Show More

Can you apply the workflow format to ISSUES / punchlist items?   For example - I have drywall that needs to be patched/repaired.  I create the issue and assign it to my drywall contractor.  Once he completes it, I need the same repair/location to now be addressed by the painter as soon as the work becomes available.  Currently, that mean creating/managing multiple issues.   It would be ideal to have the flexibility to preset the steps and assign 1 issue to multiple contractors.   ie. ISSUE - Patch/Tape/Sand/Paint Wall - 4 Days   Drywaller - 2 Days (Patch, Tape, Sand)      Painter - 1 Day - (Touch Up Paint)           GC - 1 Day - Review/Confirm Completion/ Close  Show More

If new locations are added or locations are changed, there is no way to "recalculate" the automatically determined location of an Issue placement pin on the drawing, except for manually moving the issue over by a couple of pixels. We suggest adding a button which could force this update for all issues in a project. While this can be avoided by setting up locations before any pins are placed, it would still be a useful feature if project teams do not remember to configure locations or must change location mappings. Show More

Allow project admins to set the viewing settings for Issues, including the ability to remove all columns except the drawing number and name, and to restrict users to be able to see only the current drawing version.  Show More

Have a means to assign ownership of an Issue to another person, role or company so they can assume responsibility and close the Issue. Show More

When publishing a markup linked to an issue on a sheet, the Published Markup crown icon should appear in the sheet list, just like it does for other types of published markups.   Currently, if I publish any regular markup, the crown icon appears next to the sheet name in the list, clearly indicating that there's a published markup present. However, when I publish a markup associated with an issue, this icon is not displayed, even though the markup is live and visible when viewing the sheet itself.   This seems like an oversight, as it's inconsistent behavior and can lead to confusion for project teams who rely on that visual cue to understand which sheets have published markups.   It feels like common sense that the crown icon should appear in all cases of published markups, including those linked to issues. Please consider aligning this behavior for better clarity and consistency across the platform.     Show More

Good afternoon   Kindly install a hide-all function for issues in sheets. Issues is an excellent tool to communicate improvements needed during construction. The issue is that it's used during construction, so the subcontractors/contractors/suppliers need to see the plans to finish construction, not the issue pins.  Show More

The activity log in an issue is currently quite confusing, so that it is easy to lose track. We would like to be able to filter the activity log, for example, to see only the comments like a chat or only the status changes Show More

Is there a way to customise the notifications based on the table below (please see screenshot)? Our clients are added as watchers in the issues and prefer to receive notification when an issue is created and when it’s closed at the end – they are not interested in receiving notifications for any other actions. Can we manipulate the permissions outlined in the screenshot below?   Show More