Investigating issue tracking software which could be useful for the visibility project or future projects: reasonable free options are trac and bugzilla
Bugzilla is apparently a pain to install but works well for very large projects with lots of user feedback
Trac is easier to install and maintain and has great svn integration
Jira is the best option but costs $1,400-$4,800 per server
Gave a demo to Robert A. over the whole vis suite
Meeting this afternoon about the SSP was cancelled
There seems to be a bug with the vis scripting publish feature, weird characters are being appended to the beginning of the xml. Appears to only be occurring at site.
Sent copies of the documentation to Bill and Jessica
Deployed the new visibility to the test server
Updated the reports in visibility with the new charting stuff
Investigated a bug in PPM when submitting a funding request it would not save. Appears to be a problem with string being too long to fit in the database
Scanned and deployed an update to PPM that added the duplicate copy feature
Tested the feature on the integration machine before moving to the test server
Demonstrated to Carla, Lenni, and Jessica how it works
Emailed a few or Carla’s users who were having problems, apparently they have not been granted network access which I cannot fix
Exported a list of all existing funding requests per Jessica’s request
Tried to deploy the auto-login PKI feature of visibility to the integration server but there were too many mismatches between the database, the server code, and the client, need a fresh complete version. I’ll deploy this at the same time as the chart updates
Tested the chart updates some more, seem ready to go in
Worked with Dong to produce a few queries that will be used in visibility scripting to make some reports
Building and burning to a CD copies of visibility and visibilityScripting
Compiled and tested the pki auto login functionality on the integration server. It worked for me and Jessica. I could theoretically move it to the ‘production’ server whenever. I don’t THINK it would lock anyone out.
Moved the charting package code from a sandbox project to maven flex library then compiled and deployed it.
I had to make some changes because it was compiling with Flex 4 and now Flex 3 to be compatible with Visibility.
This resulted in a few bugs and binding problems. I think I have most of them worked out but want to test some more.
Got another request on how to hide select budget centers from finance POCs while letting them see others, unfortunately the system was not designed that way so the only answer still seems to be sub-projects
Sent an email out the other 3 users having issues:
One responded that it was working now and he can also help someone else he works with
no response yet from the 3rd
Tested copying a project to create a sub-project, got a database error
Need to add some kind of banner or block to prevent users from getting on the test server since the URLs are so similar
More work on the charting package:
All the series specific configs are done
Just need a drag and drop interface for managing sets and z-order or series
