Store relevant information discovered today in your developer diary.
Description
Document the events and insights gained on your working day. This will free your mind from answering adhoc the recurring question of "Where should I add this piece of information?". The diary simply stores information to refine and add it to permanent documentation for later use.
Properties
The document type day provides the following properties:
Parent
The parent document is expected to be of type Year.
Author
A reference to the author of the day document.
Day
The normalized date of the day.
Level of Excitement
Identify your level of excitement for this day.
Mood
Identify yor mood for this day.
One Hit
The one important thing accomplished or experienced in that day.
Sections
Description
Record the important tasks and assets of a day. Add the tasks you plan for this day as a task list.
What to do for a 10 Tomorrow?
Define what can you do today to get a enthusiasm value of 10 for tomorrow.
Assets
An automatic list of assets documented for this day.
Course of the Day
An automatic list of events documented for this day.
Todos of the Day
An automatic list of t odos documented on this day.
Issues
An automatic list of JIRA issues resolved on this day.
8 Hours Burn
Have you had an effective eight hours day? Did you work more? Identify the problems, if eight hours of your life time is not enough. Speak to your agile master to get the impediments removed.
Notes
These are internal notes that are usually not exported and only visible to team members with write access.
But this is not a safe place to store sensible information. It is just a convenience for the reader to not be bothered with notes stored here for the authors for later use. The security level is about suppressing the representation by a CSS style. Therefore consider this as a convenience for the reader, not as a security tool.
References
For a document the references section contains pointers to resources that prove the statements of the document.
Often these proofs are not easily distinguishable from further information. In this case you may want to skip the reference section in favour for the resource list.
Resources
The resources section provides references to further information to the topic of the document.
This may be information on the internet provided by the resource or information in the team's information systems. Anything the reader of the resource might want to know, may be listed here.