OpsAdminIssues

Introduction

This topic cover all the issues that came up during OpsAdminVersion022. These issues fall in 3 catagories: a wishlist of usability improvents, a refactor proposal and miscellaneous. Add your 2ct!

Wishlist

• Checking LDAP integrity. There is no way to check is the projects stored in ldap are good, for example if they all have mailfolders and and if no two projects have the same id. The dao check integrity during retrieval, for example when a project id occurs twice then an error is thrown if an attempt is made to retrieve the project with that id. It would be helpful have a check-ldap button so the user knows ldap maintenance is in order.
• Better errors in the gui. When something goes wrong in the backend the user get generic, non localised errors. This is very frustrating (albeit not as frustrating as no errors, just unresponsiveness). Example: "Something went wrong when retrieving the timesheets (..)"
• Unassigned time. As part of the improvements in RemovedUnusedFunctionalityFromReportPage timesheetentries that are not liked to projects are left out of the final report. This follows requirements and makes automating reporting a lot easier but it also removes a human double check and this is bad because mistakes in timesheets will be noticed much later. The untransformed timesheets can still be exported but a check-timesheet button would help.
• Rethink authorisation: now ops_admin authorizes the individual user for ops_admin use but all the while any users is logged in to ldap as admin. Otherwise the user could not write changes in ldap. Do we want this?

Refactor: Ops integration.

All ops components connect, directly or indirectly, to LDAP. Now ops_admin does its own queries while to other components go through ops_webservices. This is is undesirable. Also, ops_adminis only ever used with the rest of ops so it makes sense to integrate the lot. A huge advantage would be the minimizing of LDAP dependency and the possibility to pick a different back-end and deploying ops would become much easier. Configuration is now smeared across a large number of .xml and .properties files. There are 2 options:

• ops_admin talks to LDAP via ops_project webservices.
• ops_admin is part of ops_project and uses the same dao

Miscellaneous

• Note that the ops_timesheet_httpproxy and ops_admin no longer use the same xsl files for transforming the ics files.
• see also bugtracker
  • New project with no imap folder, bug or feature?
  • Errormessage remains on screen bug, needs to be verified.
• In OptimizeRetrieval some extra optimization points were identified, check these if another more optimization is required.

-- IvanaCace - 02 Sep 2008