My prior work sequence: I would run "git bash" from the Windows menu & it woud start in my user directory (C:\Users\jacro); this is its default behavior. I would run cmd.exe using a shortcut so that it starts in my project directory, in this case C:\Users\jacro\devel\mlao. I have full access to this directory, because its in my user directory.
I drag one onto the other and save them as a Groupy group. I start the group and note that both shells start in C:\windows\system32. I open the .groupy files in an editor and note that there is a "WorkingDirectory" setting (I *do not* notice that this is already being ignored for Git Bash, see the original file below). I edit this entry, but with no effect.
This makes the "save group" feature of Groupy *less* convenient than just starting the two shells separately as I did before.
I had to re-create the original .groupy file, here it is (only difference from edited version is "WorkingDirectory" lines):
CommandLine="--nodaemon -o AppID=GitForWindows.Bash -o AppLaunchCmd="C:\Program Files\Git\git-bash.exe" -o AppName="Git Bash" -i "C:\Program Files\Git\git-bash.exe" --store-taskbar-properties -- /usr/bin/bash --login -i"