Allow update of existing file quotas when changing the default

Bug #821169 reported by Richard Mansfield
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mahara
Fix Released
Wishlist
Richard Mansfield

Bug Description

Reported by Tim Parkinson:

Updating the default file quota does not update the quota for existing users. This makes future administration difficult as the only way to update the file quota for existing users is to either go through them one by one and update the quotas individually, or to execute an SQL query on the database to update the settings. The number of users and presumed technical expertise of the administrators means that both of these options are not feasible.

There needs to be an option for the new quota setting to be applied to existing users. Either with an additional checkbox to say "Apply new quota to existing users" which updates the records on submit or just automatically applies the new quota to existing users.

Tags: newfeature
Changed in mahara:
status: New → Confirmed
importance: Undecided → Wishlist
assignee: nobody → Richard Mansfield (richard-mansfield)
milestone: none → 1.5.0
Revision history for this message
Mahara Bot (dev-mahara) wrote : A change has been merged

Reviewed: https://reviews.mahara.org/562
Committed: http://gitorious.org/mahara/mahara/commit/5bfb6efbb86f96482e7995e2477240ebb30bb889
Submitter: Hugh Davenport (<email address hidden>)
Branch: master

commit 5bfb6efbb86f96482e7995e2477240ebb30bb889
Author: Richard Mansfield <email address hidden>
Date: Fri Aug 5 10:28:34 2011 +1200

    Update existing file quotas when changing the default (bug #821169)

    Adds an additional checkbox to the default quota settings for users,
    groups, and institution members, which will apply the default quota
    to existing users/groups.

    Change-Id: I811bfc9902c4adb62615ea8364473174d714ddb1
    Signed-off-by: Richard Mansfield <email address hidden>

Changed in mahara:
status: Confirmed → Fix Committed
tags: added: newfeature
Revision history for this message
Melissa Draper (melissa) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 status fixreleased
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPjrXHAAoJECXBtiziiXdcU94IALII/v8XTSOgD0jBkOXYzDms
uLkrvC+Z5YqYhQVjIR5cVYg7X3SJPUjuaorS2uVVfIkGlz+38KdZdczOYV+JaNQV
S8aVo/Rqrsx8h6fKtVAgTl8bd1CCMos1YnrOTNvqoYSOV2iGSSX/paQf6R9BjDbz
hx6GM7pkUp/gOa3Zqo+E6NfUrMWASanjbh9kbHdm09L7/10f7a5Q9w2Cf5o1yjC7
xqM9hEbPe32C9tBBcXDGPzQDFpJ6b6Rys2dzt6NTNkv2FCyzKS4RLwGDUDRNBEEZ
iYxQ5wJJaxW+/RO8k4lGYSo7Mtt99aIxhkQX7DKxcEoOSNMdPUi9ptwjolgG4iI=
=AeF+
-----END PGP SIGNATURE-----

Changed in mahara:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.