ACC issues and bridged models

[pascal.robben]

Currently, we have the ability to bridge models from another ACC account for our own use, which is very helpful. However, for our project we create issues on our ACC and these are not accessible by the company who is bridging the models, it would be extremely valuable to also “bridge” issues back to the other ACC.

Why This Matters

• Improved Collaboration: Linking issues between ACC accounts would greatly enhance collaboration with external partners.
• Seamless Issue Tracking: We could maintain a direct connection between internal and external issues, making it easier to manage and track progress across platforms.
• Leverage ACC Features: This would allow both teams to benefit from all the advanced ACC issue management features, without losing context or duplicating work.

Suggested Enhancement

• Enable the ability to link or synchronize issues created in our ACC with their corresponding issues in external ACC environments.
• Provide a way to keep these issues updated in both directions, ensuring that all stakeholders are informed about the latest developments.

This feature would significantly improve our workflows and strengthen our ability to collaborate with external teams.

[jeremy.charmchizadeh]

I second this tremendously. Keeping IP separate across accounts while maintaining who did what in Build as it relates to Issues would put ACC above the rest. This is especially true for CA site observation. And on the Contractor side, they can maintain Issues between their subs while the design engineer/architect is a Watcher and be updated with work completion progress.

[david_manningQR7YW]

It is definatelly better to work more collaborativelly with projects teams by bringing them into the project with the appropriate permissions and roles. But I can also understand that this might be needed in some situations. 

[pascal.robben]

At this point additional issue management like Newforma Konekt and BimCollab are used to interact between software and different platforms. The only disadvantage of this additional software is that it cannot be used on ACC itself. Don't know if that is a limitation by Autodesk?

[rick_notari]

@pascal.robben I believe this is on the roadmap. How extensively I'm not sure.

[pascal.robben]

@rick_notari : The connection with external issue management is on the roadmap you mean?

I would expect that ACC issues would get to a point that other (extra paid) issue management wouldn't be needed anymore.

ACC is to limited, also when working with ifc's for example, the issue is hosted to that ifc and not able to open native.

[rick_notari]

@pascal.robbenYes, that’s what I meant, my apologies if I wasn’t clear. From memory, this was announced at Autodesk University during one of the ACC Roadmap sessions in 2024. Both Issues and RFIs in Autodesk Build were mentioned, and RFIs have since been released.

It will be interesting to see how the bridging of Issues will be rolled out, and whether placement will be supported initially. Based on my experience with past ACC updates, it may follow a phased rollout. That is just my opinion.