Change Issue Pin Placement

[james.marshallJC83Z]

It would be extremely useful if it was possible to change the placement of the issue pin in model coordination. Currently, once the pin has been placed on a modeled element, this can no longer be updated or changed to another element or model if required. For example, if the issue is changed to a different assignee or discipline, then the element and model pin placement should be updated to reflect this. This would also benefit the Revit Issues add-in tool allowing the correct element to be selected within the relevant model.

[tanmay.bhaleraoPRK9J]

This can be done currently via the Issues page on Docs or Model Coordination but not yet supported within Revit Issues Add-in or LMV. 

[james.marshallJC83Z]

Hi Tanmay,

Thanks for your response, however this does not change the placement of the pin to a different element in a different model, which can then be selected properly within the Revit issues addin tool. Currently, once a pin is dropped on an element in a model, it cannot be changed to a different model later on. 

Do you know if this is on the roadmap?

[tanmay.bhaleraoPRK9J]

Hi James, this can't be currently done from within the Revit Issues Add-in (not currently on roadmap but the product team has captured it as a feature request)
However, we can currently do this from the Issues page. Here's a quick screen capture where I'm changing the issue pin from and AHU in the HVAC model to the floor in Arch. Does this help? 

[james.marshall2DAZN]

Hi @tanmay.bhaleraoPRK9J 

Any update on when this feature might be available? I feel this is a really big oversight when managing issues in ACC.

You should be able to simply change the pin placement from one model to another within an existing issue in model coordination. Its an inefficient process going back into docs, selecting another model, navigating back to the area where the existing issue is located which would be extremely difficult in large models, then selecting a new location for the pin when you cant view other models.

Not having the ability to do this within model coordination or the Revit issues add in tool is significantly halting the ability to efficiently manage issues, as it can be common practice for 'Issue' responsibility to change between teams. For example, an electrical tray may not be able to move so responsibility shifts to the mechanical contractor to move a duct. In this case you would want to move the pin from the tray in the electrical model to a duct in the mechanical model, which can currently not be done easily.

Regards,

James

[tanmay.bhaleraoPRK9J]

Hi @james.marshall2DAZN - We just opened up a beta for Batch Issue Creation inside Model Coordination which includes a functionality to simply drag and move the issue pushpin in the model coordination UI. I'll DM you with some more details. 

[Siavash_Malek2EQZR]

Hi @tanmay.bhaleraoPRK9J 

Could you please advise if this has been made available yet?

Cheers,

Sia

[james.marshall2DAZN]

This is now possible to achieve through model coordination. Simply move the issue pushpin to an element in another model and it will update the 'Placement' model

[sam_deringHN7NZ]

@james.marshall2DAZN I seem to be having some errors pop up when trying to move the pin to a different model, do you know if there have been any problems since the switch to forma?

[james.marshall2DAZN]

Yeh I've also noticed this happening recently on projects... @tanmay.bhaleraoPRK9J is Autodesk aware of this and is there a fix?

[tanmay.bhaleraoPRK9J]

I doubt its related to the switch to forma. I was able to reproduce it though & checking now with the product team. It happens only when moving to a different model right? Seems to work fine when moving to another element of the same model. 

[james.marshall2DAZN]

Correct, it only fails when moving to an element in another model. Need the pin to be able to move to different models which it was previously capable of doing 

[tanmay.bhaleraoPRK9J]

The team has identified the root cause and working on a fix. I'll post another update here next week.

[twinnington]

Still an issue with changing to different model. Any update?

[tanmay.bhaleraoPRK9J]

Unfortunately, it's not done yet. The team has identified the root cause and tested that it works locally but they're going through some technical challenges when deploying/merging. I'll post an update here once it reaches the production environment.