I would suggest:

1. when setting/updating site expiry should it update the user expiry of all 
existing users (maybe not site admins)? or only newly created users?
It should go for all accounts that do not have a specific expiry date set 
already. Good idea to exclude the site admin from expiry.

2. should it override existing set expiry for user (or only if less that 
existing user expiry)?
I would not override existing specific expiry dates as someone has set those 
specifically. If we reset the expiry dates for those that have already been 
expired, their accounts suddenly become active again which should not be the 
case. Thus, see 1. Expiry for all accounts that do not have a specific date set.

3. should the setting/updating of side expiry notify affected users 
(email/internal notification)?
No. There is a second setting which you can activate letting users know when 
their account is about to expire / be set to inactive.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contrib members
https://bugs.launchpad.net/bugs/1097565

Title:
  Automatic account expiry doesn't happen

Status in Mahara ePortfolio:
  Confirmed

Bug description:
  tested on 1.6 (demo.mahara.org) and master

  When I set the default expiry (and the default inactivity) in the
  account settings, it doesn't influence anything. Not even new
  accounts. I would expect that they have the default expiry date
  displayed on the account settings page and not have "Not specified"
  ticked.

  Accounts are properly expired when set manually on the account
  settings page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1097565/+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

Reply via email to