Bug 101590 - institution expiration
Summary: institution expiration
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Academy
Classification: Retired
Component: Web Application
Version: 9
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
Assignee: Tim Burke
QA Contact: Bowe Strickland
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-08-04 15:00 UTC by Rico Hendriks
Modified: 2020-02-03 16:33 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-02-03 16:33:19 UTC
Embargoed:


Attachments (Terms of Use)

Description Luke Meyer 2003-08-04 15:00:26 UTC
when an institution's enablement expires, it should be handled, not just cause
errors.  what effect it *should* have isn't clear.  for starters, the
institution manager should probably see a notice that it's disabled and nothing
more.  What about class instructors or students?

Comment 1 Bowe Strickland 2003-08-04 15:09:02 UTC
my thoughts...

gls and institution mananger should get emailed 2 weeks before expiration, 
1 week before expiration, and 2 days before expiration.  emial should
include a list of any active classes this will cause problems for (though end
date of class should already have been pinned to end date of institution).

upon expiration, classes should become "inactive" (though i'm not sure we've
hammered out exactly what that means, either ;)  



Comment 6 James Hartsock 2015-03-18 15:16:08 UTC
*** Bug 1022196 has been marked as a duplicate of this bug. ***

Comment 8 Tim Burke 2020-02-03 16:33:19 UTC
Please resubmit if this is still an issue.


Note You need to log in before you can comment on or make changes to this bug.