Opened 13 years ago
Closed 13 years ago
#235 closed enhancement (fixed)
Advise groups to watch for a reply from CAC
| Reported by: | adehnert | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | Sometime |
| Component: | Space | Version: | |
| Keywords: | Cc: | ||
| Size: | tiny |
Description
As a low-tech alternative (or supplement) to ASA-#209, we could advise groups in a note at the bottom of the emails to follow up with CAC if they haven't heard anything about a request in more than, say, a week. (See also https://diswww.mit.edu/menelaus/asa-db/12084.)
Change History (3)
comment:1 Changed 13 years ago by adehnert
comment:2 Changed 13 years ago by adehnert
Fixed (mostly) by commit 210d0423925650b4a4d839b985dd9c887614ef56:
Author: Alex Dehnert <adehnert@mit.edu>
Date: Sun Jun 2 19:18:06 2013 -0400
Space: tell groups CAC should reply (ASA-#235)
CAC generally does a great job handling office access updates quickly, but
occasionally some requests slip through the cracks. Add some text to tell
groups to expect a reply from CAC, so they can use that to tell their group
members if access should work, and also so that they can contact CAC if a
request seems to have gotten lost.
Remaining: add an actual interval.
comment:3 Changed 13 years ago by adehnert
- Resolution set to fixed
- Status changed from new to closed
Interval added in commit 72a3d909f895d5891dd1a80bffde4b79e48cc640:
Author: Alex Dehnert <adehnert@mit.edu>
Date: Tue Jun 4 17:16:50 2013 -0400
Fill in the office access timeframe
See also https://diswww.mit.edu/menelaus/asa-db/12660. There are two applicable
times; rather than try to explain the difference, just go with the longer one.
Note: See
TracTickets for help on using
tickets.
Oh, sufficiently APO-like people can also look at https://diswww.mit.edu/charon/apo-printshop/6666.
(Edit: "sufficiently APO-like" apparently means "anybody".)