It's certainly powerful, but too complex for most designers who just need one number to identify a Revision/Change/Issue. Having no discernible connection between the Change Manager and the Issue Manager leaves us having to choose between one or the other, or else you're entering redundant information for no reason. And most people, under deadlines, simply don't do it, resulting in a mess.
We desperately need an "EASY" button somewhere that makes Change = Revision = Issue. We can already do this with Revision = Issue, so it's just one more step. Create a Change, it creates a corresponding Issue.
We've been fighting with this tool for two years now, and I even taught a LearnVirtual webinar on using the Issue Manager only, ignoring changes, for simplification. However, now I'm finding that the other way around may be easier. Either way, it feel like I'm constantly re-inventing this wheel.
Chuck Kottka
Orcutt Winslow
Phoenix, Arizona, USA
ArchiCAD 25 (since 4.5)
Macbook Pro 15" Touchbar OSX 10.15 Core i7 2.9GHz/16GB RAM/Radeon Pro560 4GB