I guess if we want to ensure that groups created via web services are treated differently, that should go for other settings in the group then as well and not just the short name as you can also control other settings.
Groups created via CSV files could be a bit trickier as there are two use cases: 1. Permanent management of groups via CSV file -> These should not have group short names changed. 2. Initial upload of groups via CSV but no further intention of managing them via CSV -> These could have group short names changed. In regard to the CSV file groups, I would say that we can expect administrators to download the CSV files from Mahara before making changes to the groups as that is the status quo on the site. Otherwise, it might get too complicated to manage. -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1722180 Title: Unable to edit shortname of copied group Status in Mahara: Confirmed Bug description: Using an existing group on 17.04 as a template for a new group with a similar layout. The shortname is created by default and greyed out so cannot be changed. From copying a group that was called BVMSclassof2021 I now have BVMSclassof2021a and BVMSclassof2021aa for the shortnames of group that don't even relate to that programme or year, but can't see any way to edit it (without accessing back-end db, which I'm not allowed to do). Thanks, Gordon. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1722180/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
