Date: Fri, 29 Mar 2024 15:47:15 +0100 (CET) Message-ID: <925302701.17974.1711723635521@09e9d69a2016> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_17973_1417359612.1711723635520" ------=_Part_17973_1417359612.1711723635520 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Associated an event with = a day. A event is a collection of associated information for your later ref= erence. Information may further be organized by subject, tags, categories, = and audience.
The event contains a piece of information that may be of interest in the= future. A day is typically a= flow of events and each event is in its own event document. That way the e= vents may be referenced easily by a link.
While the event document my feel like a form at first glance, it is not.= All properties= a> (besides name and short description) and= sections are -= as always with the projectdoc Toolbox - strictly optional. But some of the= m are very handy to quickly organize events and add references to related i= nformation.
The document type event provides the following properties:
Please note that only information about specific properties is provided = here. Common document property used by all document types are documented by= Document Propert= ies.
Document the type of th= e event.
Provide a link to an event this event continues with. Sometimes topics a= re investigated over a number of days. With pointing to the last event of i= nvestigation the flow of events on a very specific topic is easier to looku= p later.
List the stakeholders<= /a>, organizations, = or persons that participat= e in this event.
This makes it easier to track events on the participants' documents chro= nologically.
Since 7.0.0
This section is available since version 7.0.0.
Add links to documents that refer to entities this event is concerned wi= th.
If you are configuring a system or service= , or follow a work i= nstruction, this can be referenced for further information. It also ide= ntifies the entities unambiguously.
Since 7.0.1
This section is available since version 7.0.1.
Add a link to a todo docu= ment this event is related to. The reference may point to any document that= serves as a folder for documents belonging to that file.
Since 7.0.0
This section is available since version 7.0.0.
A rating on how much fun this event provided.
All things to remember about this event goes in here.
Document the result of your work. Are there open issues or has the task = been completely resolved?
If there are assets you = want to refer to individually, then add asset documents to this event. Thes= e documents will be listed automatically in the next section.
Since 7.0.1
This section is available since version 7.0.1.
A list of assets y= ou need to reference explicitly from other documents or you simply want to = document separately from this event.
Document the intermediate steps of your work that led to your result.
This may help you and others in the future to reevaluate the path to you= r solution.
You may add open issues as to= dos to this document. These todos will be automatically listed in the n= ext section.
Since 7.0.1
This section is available since version 7.0.1.
A list of todos
In case you add documents of any other type than event as child to this = page, they will be automatically shown in this section. Again, this is usef= ul if you need to make references to these pieces of information or you wan= t to document them separately.
In case you need to divide the information of this event in several even= ts. The only reason to do so is to have each subordinate event referable by= its own URL.
This section lists the events that have previously dealt with the same p= iece of work. This is a listing of the "Continuation of" information.
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 informat= ion. 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 supp= ressing the representation by a CSS style. Therefore consider this as a con= venience for the reader, not as a security tool.
The text of notes sections is also indexed.
For a document the references section contains pointers to resources tha= t prove the statements of the document.
Often these proofs are not easily distinguishable from further informati= on. In this case you may want to skip the reference section in favour for t= he resource list.
For further information please refer to References and 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 info= rmation in the team's information systems. Anything the reader of the resou= rce might want to know, may be listed here.
For further information please refer to References and Resources.
Name | Short Description |
---|---|
Annual Vision |
Describe your vision for one year. You plan will help you stay focussed = to accomplish your goals. |
Annual Vision Type |
Categories for annual visions. |
Asset |
Explain an asset of your work. Add this document to a day in your diary.
|
Asset Type |
Categories for assets. |
Cheat |
A brief solution to a problem. |
Cheat Type |
Categories for cheats. |
Day |
Store relevant information discovered today in your developer diary. |
= Day Type |
Categories for days. |
Diary= |
The homepage of a developer's daily diary pages. Consider to add your diary=
to your personal space!
|
Diary Type |
Categories for diaries. |
Event Type |
Categories for events. |
Month |
Plan and run a retrospective for your month of work. |
Month Type |
Categories for months. |
Todo |
Add a todo note to your developer diary. |
Todo Type |
Categories for todos. |
= Vision |
Describe your vision for your career. |
Vision Type |
Categories for visions. |
Week |
Plan and run a retrospective for your week of work. |
Week Type |
Categories for weeks. |
Year= |
Create a year in your Diary. |
Year Type |
Categories for years. |