The change log is an embedded sub-form in the Change Request form. This form is for recording technical details about implementation. Because it is embedded in the Change Request form, it's handy to know how to search for a specific record. The Search Record # lets you enter the request number you are looking for. At the bottom of the form, you can use the navigation tools to flip through all of the records.
1) Once a request is approved, it should be assigned as soon as possible.
2) date of the assignment. Don't fill this in unless the person in field 1 is aware of whats going on!
3) notes, ideas, trial and error and most importantly, what worked.
4) was the change tested (the sandbox Specify database, giving a new volunteer the wiki to read etc) and results.
5) This is mostly in regards to databases, but as a more general guideline this is where bottlenecks are identified. ('I need to wait for Angie to finish the wiki before I can proceed with this). If you are waiting on a person to finish something, give them a heads up.
6) Date the bottleneck/dependency is resolved.
7) any extra information
8) Completed by will probably be the same as the 'assigned to' person.
8a) Document the changes that were made- we need the 'hows' of what was done- in case you win the lottery and run away to an isolated tropical island, someone will be able to read your documentation and update your project in your absence.
8b) Once documentation is complete, you can fill in the date completed box.
