I'm working on scientific software. The users are engineers and physicists, not consumers.
It's a non-web, Windows app. The client is Java Swing.
It has an Edit menu with the usual clipboard actions on it: Copy and Paste. These are rarely used on text, however. Mostly they are for pasting some scientific object like a physics continuum from one part of a physics simulation to another. (That's why Cut is rarely supported.)
These Copy and Paste actions also appear on our Context Menus. (I mean menus that pop up when you right-click an object.)
Our Context Menus are sometimes long. They have many menu items, sometimes more than 10.
In some cases, we know that the Copy and Paste actions are very rarely performed.
I am considering removing the Copy and Paste menu items from a Context Menu if and only if we have reason to believe that those Copy and Paste actions are rarely performed. They would still be available via the Edit menu and keyboard shortcuts.
My reasoning is that they clutter up the menus. Shouldn't a Context Menu support actions that a user is likely to perform in a specific context?
On the other hand, I want the software to be consistent, both internally and with a user's expectations based on other Windows software.
Colleague A says We must support copy and paste on the Context Menus. These appear ubiquitously across Windows software like Word, Powerpoint, Firefox...
Colleague B says We must declutter our Context Menus. Specialized apps like Photoshop don't support every common Windows UI feature...
What should I do?