Bug #49431 Routine groups seems busted

Description:
I'm not sure what "routine groups" actually are; they appear to be an invention of the WB team, and there is no support for them within MySQL server proper.  I tried reading through http://dev.mysql.com/doc/workbench/en/wb-routine-groups.html to see exactly how they are intended to be used, but it remains unclear.

I thought that maybe I would figure it out if I performed the actions described on the page, but I cannot.  I can add a new routine group, but that opens the routine groups editor, and there are no routines available (despite having first defined one).  The "Routines" tab has the following:

-- --------------------------------------------------------------------------------
-- routines1 Group Routines
-- --------------------------------------------------------------------------------
DELIMITER //

I cannot drag and drop routines, despite what the documentation suggests.

I also cannot copy or cut the routine group.

How to repeat:
See above.

Suggested fix:
See above.

Can't drop #1

Attachment: SP32-20091203-140650.gif (image/gif, text), 49.70 KiB.

Can't drop #2

Attachment: SP32-20091203-140701.gif (image/gif, text), 55.86 KiB.

Can't cut/copy

Attachment: SP32-20091203-140738.gif (image/gif, text), 81.07 KiB.

It seems that sometimes these things are enabled, and sometimes they are not.  Going back to the same exact model, I can now add routines to the routine group using drag-and-drop, and the cut/copy options are available.  No idea what drives this, seems fairly random.

I was easily able to repeat this on Ubuntu.

Works fine in Linux, will check Windows.

Also works fine in Windows. Are you sure you're drag/droppping Routines instead of Routine *Groups*?
You can't drag/drop a routine group inside of another, only routines. The screenshots kind of suggest you're trying the later.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".