Issues Pin Placement

[Jhansi_Ravi]

Hello team

Our proposal is Issues pins to embed within the file and not stay in particular place/page where they have been raised. Embedding helps to track the issues in previous version(V1) and current version(V2), rather then pins staying in same place. This is causing our team to go back to pervious version(V1), and find where the actual issue is in current version(V2).

For example:

If issue is raised in page 2 line 10 of the file. When we have new version uploaded with more pages or amended pages, actual issue moves from page2 line10. So, the actual issue in new version will be in different place, but the pin points to page2 line 10. Now, we have look for where the original issue was.

Our Proposal: Embedding the issue pin within the file for easier tracking. 

Thank you.

Jhansi

[jaroslav.pancocha]

I am not sure if it is same problem, but i could really help in many cases if issues are not pinned to "some" place, but object. F.e. if I pin issue to one end of the beam, this issue should be then visible in all views, where is this beam visible.

[Ezekiel12]

This should be implemented out of the box already. Seems like totally basic function. F.e. How else do you want to good cooperation and coordination to work when You need several windows opened and check manually WHERE the pin is in 3D and where it should be in 2D?