Requests from Individual Campuses:
1. At CU Boulder we would really like AD/LDAP failover to function within Confluence (dynamic failover). As it is now, on patch Tuesdays we have to manually shut down Confluence and restart it to failover to another Domain Controller. There are feature requests in for this at Atlassian.
2. At MIT, some instructors may wish to have their wiki space span semesters. This poses potential problems with regard to student privacy since a student in the Spring 2008 incarnation of the course may see identifiable postings of students in the Spring 2007 class. We could have students sign a disclaimer up front, but this would be difficult to do and pretty much of a nightmare to track. Another solution would be to have a rule that can be invoked at the space or page level and that says something like 'for postings (and attachments and comments) prior to date x, if the current user is not the user associated with the posting (or attachment or comment) and is not a space admin, substitute a generic identifier (e.g. 'Student 1') rather than the name associated with the poster'. We wouldn't want to modify the database, just the display.
23. At MIT we would like to have the ability to, in an otherwise restricted space or page (no anonymous access), provide the ability for a person to choose to post/edit/comment/upload anonymously. A class is currently using Confluence to construct a collaborative poem, and the instructor suggests that anonymity would change the dynamic of how students edit. E.g. Sally might be hesitant to wipe out her best friend Tom's latest contribution knowing it's his. This functionality could be useful in other contexts (e.g. suggestion box) as well.
...