This is an informal report I received about usability issues found by a prospect using the new groovy module. This story just gathers them all and there will probably be sub-tasks as appropriate for the reported issues.

• if i create new script, it opens window for me where i can edit it, but if i want to do "class" I have to call that class untitled (the name of the script) otherwise compilation fails. If I had "untitled" script there already, it might be "untitled0" or some other number, so i might not even know how to call my class. FIXED
• when I rename script, and it happens to be a class, i have to open it and rename class too. FIXED
• when I move script, and it happens to be a class, i have to open it and fix package declaration.
• to make things worse, in case of class, if I hit "save" button and there is an error, i get error notification, but "save" button stays disabled so I can't save it again, I have to cancel, reopen and redo my change. FIXED
• I can't add scripts under scripts, but that's exactly what my.commands.MailCommand uses. not folders, but scripts. FIXED
• While I can't create scripts under scripts, I can easily move scripts under other scripts. FIXED
• When editing, I can make edit window (code press) expand to the full width, but not to full height of the page. FIXED by MGNLUI-2266
• I can't version my scripts and can't compare versions to see what I have changed in the past
• While I can export script as an xml, I would like to be able to export it also as a text file instead of having to open it, select all, copy, open text editor, paste, save.