mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

On further reflection we will need to differentiate between
* auto-created groups via web services / CSV files - should not be able to change shortname
* manually created / copied groups - should be able to change shortname

If we do leave it up to group admins to be able to change shorname, I'd
say it would need to be any group admin.

We should also allow the changing of the name / shortname via the
Administration -> Groups -> Manage configuration screen. That way the
site admin does not need to be a admin of the group to change these two
values.

They would / should know if there was some auto-process involved in
setting up the group when editing them.

-- 
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