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

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

Add Working days and calendar days options to all tools for Due Dates, its available in the submittal tools and we action an issue add a 5 day lead time for close which is sometimes on the weekend days. Show More

Test for support Show More

We've noticed that we often receive bids from general contractors located across the country. While we understand that this is how the platform is designed, our experience over the years has shown that working with GCs outside of the New England area tends to be less successful for several reasons. One of the biggest challenges is during the final billing stage—these companies are often no longer actively engaged with the project and typically lack a local presence or office we can contact. This makes collections difficult and, in cases where legal action becomes necessary, it turns into a logistical nightmare trying to pursue claims against out-of-state entities. Ideally, we’d like the ability to filter or select the geographic regions where we’re open to receiving bids—similar to how service areas are set when initially setting up an account on Building Connected. Whether by choosing specific states or mapping out preferred regions, this feature would help us focus on building relationships with contractors who are more aligned with our area of operation and who can better support the project through closeout. Show More

As far back as when the Model Coordination views had a Model Browser panel, there had been a duplication of Model Tree functionality. There was a Model Tree on the Model Browser panel, as well as an older Model Browser floating panel from the view's bottom toolbar.   Recently, the Model Browser on the toolbar went away. And with that removal was also a degradation of workflows. This is a similar problem as the Levels panel.   There are two problems with the current Model Browser functionality. It has lost its ability to remember object visibilities. When you hide objects in this panel using the Model Tree, as soon as you change to another tab those objects are unhidden. This makes it impossible to set object visibility prior to creating an Issue. Even if the object visibility is retained when traversing panels, the effort required to interact within this space has now increased. For example, in a review session where many Issues may be raised, we may need to control the visibility of objects before placing an Issue Pin. There is now a constant switching required between the Model Browser panel and Issues panel. Much like the Levels idea linked above, please move the Model Tree back to being a floating panel. Show More

Autodesk Construction Cloud Case Number : 02122981 I have heard back from our Engineering team who have confirmed that this is intended behavior for the platform as attachments has more limitations. In order to be able to zoom in or out you will need to add the photos to the Issue as a reference instead of an attachment. We encourage you to submit your idea directly to our R&D team via the ACC Forums here. Our ACC R&D team actively monitors these forums and considers customer suggestions for future development and prioritization.  Show More

When an issue is created, I would like to send it to another member of the project other than myself to allow them to attach it to a Work Request for the employee or contractor.          Show More

It's currently impossible to assign issues to unasigned roles. This would be usefull in case someone wants to prepare a set of questions for a yet to be decided project memeber. Maybe said member still needs to be introduced to the platform, so they haven't been added yet until they receive a proper explination of how things work. Like when a general contractor wants to initiate an ACC environment and he has received the projectfiles. His team might want to start analysing stuff, but the Architect hasn't been added yet until he knows whats what.   Or a designer might want to prepare a set of issues when designing a project where he wants to query the contractor or subcontractor how he would prefer to tackle a problem with multiple viable solutions.   Currently the only way to do this is to add a throwaway superuser to your project with all unasigned roles. However this means projectmembers can adres the superuser instead of the role, so when the propper person gets added they might not receive all issues which they need to see. Additionally these users should always receive a summary of all issues and notifications they might still have to adress when they get added to the project. Show More

With only a picture on the PDF, it's hard to explain what and where the interference is.   It's often unrealistic to expect reviewers to fully memorize others' drawings and 3D views before checking issues. As a result, I frequently need to crop and attach partial screenshots from related drawings manually. It would be very helpful to support marking partial views from multiple models and drawings directly within the issue, which could greatly reduce the need for manual screenshots.   And I think this is a relative idea. https://forums.autodesk.com/t5/acc-ideas/let-user-place-an-existing-issue-on-the-current-view/idi-p/13313745 Show More

When a drawing or a document is replaced with a new version, it's still possible to create an issue on the already open  file. As the browser is not automatically refreshed, a user can keep creating issue on the old file version without knowing there is a new one. This results in issues that will not appear on the last file version. So that, another user can miss them. In this case,  ACC browser should either poll the server regularly and let the user know there is a new version (without having to manually refresh or reopen the file), either it should prevent the user to create an issue on an old file version.  Show More