Controls the location of the homepage of a given document type. Use the identifier of the doctype.

Tags: Homepage Property
Identifier: projectdoc.doctype.(doctype).home
Data Type: link

Controls the location of the homepage of a given document type. Use the identifier of the doctype.

This selection is activated via the document wizard. Select the "Send to Homepage" checkbox to save the new page to the defined homepage.

The value of this property is either the title of the homepage (if the homepage is in the same space as this space property definition) or space key and title (as in SPACEKEY.Page Title).

Since version 2.0 of the projectdoc Toolbox it is also allowed to use a Confluence link to the wiki page.

Doctype Identifiers

The identifiers for the doctypes are:

Name	ID	Doctype Add-on	Short Description
Introduction and Goals	`swad-section`	arc42	The first chapter of the arc42 Template with information on requirements, quality goals, and stakeholders.
Architecture Constraints	`swad-section`	arc42	The second chapter of the arc42 Template with information on constraints and conventions.
System Scope and Context	`swad-section`	arc42	The third chapter of the arc42 Template with information on context and external interfaces.
Solution Strategy	`swad-section`	arc42	The fourth chapter of the arc42 Template explains the solution idea.
Building Block View	`swad-section`	arc42	The fifth chapter of the arc42 Template with information on the local building blocks, and their dependencies and relationships.
Runtime View	`swad-section`	arc42	The sixth chapter of the arc42 Template with runtime information about the architecture.
Deployment View	`swad-section`	arc42	The seventh chapter of the arc42 Template with information about how the system is deployed.
Cross-cutting Concepts	`swad-section`	arc42	The eighth chapter of the arc42 Template with conceptional information about the system.
Design Decisions	`swad-section`	arc42	The ninth chapter of the arc42 Template that explains the architecture decisions that led to the system.
Quality Requirements	`swad-section`	arc42	The tenth chapter of the arc42 Template that lists scenarios to systematically evaluate the architecture against the quality requirements.
Risks and Technical Debts	`swad-section`	arc42	The eleventh chapter of the arc42 Template lists risks and technical debt.
Glossary	`swad-section`	arc42	The last chapter of the arc42 Template lists terms of the domain and explains them.
Access Information	`access-information`	Service Management	Credentials for development systems where the password is known to all who have access to the Confluence wiki.
Access Information Type	`access-information-type`	Service Management	Type-specific category for access information.
Alternative	`alternative`	Project Management	This documents a possible option for a decision. Choose this document type to describe the alternative for a decision in more detail. This is typically a subpage of a decision document.
Alternative Type	`alternative-type`	Project Management	Group your alternatives by a self-defined type.
Announcement	`announcement`	Agile Team	Announcements are a way to communicate an important piece of information with your team.
Annual Vision	`annual-vision`	Developer Diaries	Describe your vision for one year. You plan will help you stay focussed to accomplish your goals.
Annual Vision Type	`annual-vision-type`	Developer Diaries	Categories for annual visions.
App	`app`	App	Document your app for your users and customers.
App Component	`app-component`	App	Provide more detailed information about a component of a tool.
App Component Type	`app-component-type`	App	Document the purpose and usage of the components of this type.
App Extension	`app-extension`	App	Document your extension for your users and customers.
App Extension Type	`app-extension-type`	App	Document the purpose and usage of the extension of this type.
Application	`application`	Service Management	Applications provided functions required by services. Applications may be hosted on one or more systems.
Application Type	`application-type`	Service Management	Type-specific category for applications.
App Macro	`app-macro`	App	Document the purpose and usage of the macro.
App Macro Type	`app-macro-type`	App	Document the purpose and usage of the macros of this type.
App Parameter	`app-parameter`	App	A parameter is a configuration option. Parameter exist on different layers. Wizard and macro parameters are configuration options. Use parameter types to organize them!
App Parameter Type	`app-parameter-type`	App	Document the purpose and usage of the app parameters of this type.
App Platform	`app-platform`	App	Document a platform for apps.
App Platform Type	`app-platform-type`	App	Document the purpose and usage of the platforms of this type.
App Service	`app-service`	App	Document a service provided by an app.
App Service Type	`app-service-type`	App	Document the purpose and usage of the app services of this type.
App Tool	`app-tool`	App	Document a tool provided by an app.
App Tool Type	`app-tool-type`	App	Document the purpose and usage of the app tools of this type.
App Type	`app-type`	App	Document the purpose and usage of the apps of this type.
arc42 Template	`swad`	arc42	The blueprint of the arc42 Template creates a tree of pages in the Confluence space.
Architecture Alternative	`architecture-alternative`	Software Development	Document a possible option for an architecture decision. Choose this document type to describe the alternative for a decision in more detail. This is typically a subpage of an architecture decision document.
Architecture Alternative Type	`architecture-alternative-type`	Software Development	Group architecture alternatives by their type.
Architecture Aspect	`architecture-aspect`	Software Development	Document an aspect of your architecture. Something orthogonal or cross-functional like logging, exception handling or configurability.
Architecture Aspect Type	`architecture-aspect-type`	Software Development	Group architecture aspects by their type.
Architecture Decision	`architecture-decision`	Software Development	Document a architecture decision for an option. This is useful to state the reasons and the options that have been evaluated. Later other team members will have it easier to understand the decision.
Architecture Decision Type	`architecture-decision-type`	Software Development	Architecture decisions are group by their types. A commonly used decision type is 'Architecture'.
Artifact	`artifact`	Software Development	Document requirements you impose on artifacts. Artifacts are created by processes defined and used by the team. This includes assemblies created by the build process, source code artifacts or reports.
Artifact Type	`artifact-type`	Software Development	Artifact types categorize artifacts.
Asset	`asset`	Developer Diaries	Explain an asset of your work. Add this document to a day in your diary.
Asset Type	`asset-type`	Developer Diaries	Categories for assets.
Association	`association`	Core	Associates two documents.
Association Type	`association-type`	Core	Categorize associations by a type.
Assumption	`assumption`	Risk Management	Document assumptions to assess risks and opportunities for the project.
Assumption Type	`assumption-type`	Risk Management	Assumptions are grouped by their type.
Blackbox	`blackbox`	Software Development	Describe as a Blackbox the elements of a view where only the externally visible properties are relevant.
Blackbox Type	`blackbox-type`	Software Development	Group blackboxes by their type.
Blank Document	`blank`	Native	The blank template simply provides a minimal integration with projectdoc features. It is a quick starting point to use projectdoc.
Bookmarklet Editor	`bookmarklet-editor`	Bookmarklets Extension	The bookmarklets editor is a simple page that allows teams to create their bookmarklets more easily. It also provides access to some standard bookmarklets provided for the projectdoc Toolbox.
Category	`category`	Core	Categories allow to set document instance of different doctypes in a hierarchy.
Category Type	`category-type`	Core	Categorize categories by a type.
Change	`change`	Service Management	Document a single change to configuration items or assets.
Change Severity	`change-severity`	Service Management	Add an severity to classify changes.
Change Status	`change-status`	Service Management	Add a status to categorize changes.
Change Theme	`change-theme`	Service Management	Add a theme to group changes.
Change Type	`change-type`	Service Management	Type-specific category for changes.
Charter	`charter`	Core	Describes an information need and use this description as a basis to create and maintain a document.
Charter Type	`charter-type`	Core	Categorize charters by a type.
Cheat	`cheat`	Developer Diaries	A brief solution to a problem.
Cheat Type	`cheat-type`	Developer Diaries	Categories for cheats.
Checklist	`checklist`	Teamwork	Checklists allow to run manual tasks in a defined manner. It guides the user of the checklist through a process and helping to not forget a step.
Checklist Type	`checklist-type`	Teamwork	Categorize checklists by type.
Code	`code`	Software Development	Describe the codes that are part of the product's API.
Code Type	`code-type`	Software Development	Code types categorize codes, used in logging or exception handling.
Component	`component`	Software Development	Components are part of a view on a system. A component may refer to a enclosed element or to a complete system of its own.
Component Type	`component-type`	Software Development	Component types categorize components.
Configuration Item	`configuration-item`	Service Management	Configuration items (CIs) may be (sub-)systems or components. Whatever may change and needs to be tracked may be documented as a CI.
Configuration Item Status	`configuration-item-status`	Service Management	Signals the status of an IT system, application, or a configuration item.
Configuration Item Type	`configuration-item-type`	Service Management	Type-specific category for configuration items.
Cycle	`cycle`	Core	Add cycles to group cycle phases.
Cycle Phase	`cycle-phase`	Core	Cycle phases define phases that are bound to a cycle, such as lifecycles or iterations.
Dataset	`dataset`	Service Management	Datasets are used as the input and output of processes.
Dataset Type	`dataset-type`	Service Management	Type-specific category for datasets.
Data Type	`datatype`		Document a data type for properties and codes.
Data Type Type	`datattype-type`	Software Development	Data type types categorize data types.
Day	`day`	Developer Diaries	Store relevant information discovered today in your developer diary.
Day Type	`day-type`	Developer Diaries	Categories for days.
Decision	`decision`	Project Management	Document a decision for an option. This is useful to state the reasons and the options that have been evaluated. Later other team members will have it easier to understand the decision.
Decision Type	`decision-type`	Project Management	Group your decisions by a self-defined type.
Deployment	`deployment`	Service Management	Deployments provide information about updates on services and systems to users.
Deployment Record	`deployment-record`	Service Management	Record a deployment to a IT system.
Deployment Record Type	`change-type`	Service Management	Type-specific category for deployment records.
Deployment Type	`deployment-type`	Service Management	Type-specific category for deployments.
Diary	`diary`	Developer Diaries	The homepage of a developer's daily diary pages. Consider to add your diary to your personal space!
Diary Type	`diary-type`	Developer Diaries	Categories for diaries.
Doctype	`doctype`	App	Document the usage of a doctype for your users.
Doctype Type	`app-doctype-type`	App	Document the purpose and usage of the doctypes of this type.
Document Property	`document-property`	App	Document the usage of a document property for your users.
Document Property Type	`document-property-type`	App	Document the purpose and usage of the properties of this type.
Document Section	`document-section`	App	Document the usage of a document section for your users.
Document Section	`document-section-type`	App	Document the purpose and usage of the sections of this type.
Environment	`environment`	Software Development	Document logical or physical groups of nodes.
Environment Type	`environment-type`	Software Development	Type of an environment used by the project to deploy the application or the solution.
Event	`event`	Developer Diaries	Associated an event with a day. A event is a collection of associated information for your later reference. Information may further be organized by subject, tags, categories, and audience.
Event Type	`event-type`	Developer Diaries	Categories for events.
Excerpt	`excerpt`	Core	Excerpts are abstracts of information found in a resource, such as a book. If you want to go into more detail for a given resource, there may be multiple excerpts as subpages of the resource document.
Excerpt Type	`excerpt-type`	Core	Categorize excerpts by a type.
Experience Level	`experience-level`	Core	Defines the context through which readers acquire skills. The level sets the expectation on the author's techniques to teach.
Experience Level Type	`experience-level-type`	Core	Categorize experience levels by a type.
FAQ	`faq`	Core	FAQs help to record an answer to a frequently asked question concerning the project, the product, the system or the process.
FAQ Type	`faq-type`	Core	Categorize FAQs by a type.
Feature	`feature`	Software Development	Documents a feature of the product. The top features define the main aspects of the product.
Feature Type	`feature-type`	Software Development	Feature types categorize features.
Generic	`generic`	Core	Generic Documents provide information where no other doctype matches.
Generic Type	`generic-type`	Core	Categorize generic documents by a type.
Glossary Item	`glossary-item`	Core	Glossary items are part of the domain glossary for the project. Glossaries support the team to use terms of the domain consistently in conversations and documentation.
Glossary Item Type	`glossary-item-type`	Core	Categorize glossary items by a type.
Improvement	`improvement`	Agile Team	Improvement proposals help to start the conversation within the team for process improvements.
Interface	`interface`	Software Development	Interfaces document how elements of the system communicate with elements of this and other systems.
Interface Type	`interface-type`	Software Development	Group interfaces by their type.
IT Activity	`it-activity`	Service Management	IT Activities define activities for processes.
IT Activity Type	`it-activity-type`	Service Management	Type-specific category for IT activities.
IT Asset	`it-asset`	Service Management	IT Assets define assets required or produced by processes.
IT Asset Type	`it-asset-type`	Service Management	Type-specific category for IT assets.
Iteration	`iteration`	Agile Team	Document an Iteration that may be linked from JIRA. Allows the team to set the goal and add notes relevant to a particular iteration.
IT Function	`it-function`	Service Management	Functions are specialized organizational units to support business processes.
IT Function Type	`it-function-type`	Service Management	Type-specific category for IT functions.
IT Procedure	`it-procedure`	Service Management	IT Procedures define procedures for processes.
IT Procedure Type	`it-procedure-type`	Service Management	Type-specific category for IT procedures.
IT Process	`it-process`	Service Management	Processes organize activities to create a defined business value.
IT Process Type	`it-process-type`	Service Management	Type-specific category for IT processes.
IT Service	`it-service`	Service Management	IT Services provide business relevant services for customers.
IT Service Classification	`it-service-classification`	Service Management	Classifiers to categorize services.
IT Service Classification Type	`it-service-classification-type`	Service Management	Type-specific classification for IT services.
IT Service Status	`it-service-status`	Service Management	Signals the status of an IT Service.
IT Service Type	`it-service-type`	Service Management	Type-specific category for IT services.
IT System	`it-system`	Service Management	Systems are part of environments where products are deployed to.
IT System Type	`it-system-type`	Service Management	Systems are categorized by their type. These types may be quite concrete since systems by nature reference a hard- or software system usually by their IP address or DNS name. Therefore a system type may be 'Artifact Repository' or 'Virtual Server. And types may build hierarchies.
Lifecycle	`lifecycle`	Service Management	Add lifecycles to group lifecycle phases.
Lifecycle Phase	`lifecycle-phase`	Service Management	Lifecycle phases define phases that are bound to a lifecycle.
Location	`location`	Service Management	Locations provide information about the whereabouts of assets, configuration items, and systems.
Location Type	`location-type`	Service Management	Type-specific category for locations.
Media Type	`mediatype`	Core	Resources are identified by their media type. This may be the MIME type, but also a human readable string, that identifies the syntactic format.
Media Type Type	`mediatype-type`	Core	Categorize media types by their type.
Metadata	`metadata`	Core	Metadata documents provide tables of simple key/value pairs. This information can be used as an aspect or as additional space properties to be available for reference on your wiki.
Metadata Type	`metadata-type`	Core	Categorize metadata documents by a type.
Minutes	`minutes`	Project Management	Record the action items of a meeting.
Minutes Type	`minutes-type`	Project Management	Group your minutes by a self-defined type.
Mission Statement	`mission-statement`	Business Strategy	Define a mission for your company or product.
Mission Statement Type	`mission-statement-type`	Business Strategy	Type-specific category for mission statements.
Module	`docmodule`	Core	A documentation module is a fragment which is usually transcluded by other documents. The lifetime of a module document is independent of the lifetimes of the documents that reference it.
Module Type	`module-type`	Core	Categorization of document modules for single sourcing.
Month	`month`	Developer Diaries	Plan and run a retrospective for your month of work.
Month Type	`month-type`	Developer Diaries	Categories for months.
Node	`node`	Software Development	Nodes are part of environments where artifacts are deployed to.
Node Type	`node-type`	Software Development	Node types categorize nodes.
Open Issue	`open-issue`	Project Management	Open issues document what the team needs to know to proceed.
Open Issue Severity	`open-issue-severity`	Project Management	Open issues are grouped by the severity of their impact on the project.
Open Issue Status	`open-issue-status`	Project Management	Open issues are grouped by the status.
Open Issue Type	`open-issue-type`	Project Management	Group your open issues by a self-defined type.
Opportunity	`opportunity`	Risk Management	Document and track identified opportunities for the project.
Opportunity Type	`opportunity-type`	Risk Management	Opportunities are grouped by their type.
Organization	`organization`	Core	Information about organizations that take a part in the project. You may collect common information here for all persons that belong to an organization, such as address or homepage.
Organization Type	`organization-type`	Core	Categorize organizations by a type.
Out Item	`out-item`	Software Development	Out Items record topics that are out of the scope of the project. This is useful for project inception and for reference in the future.
Out Item Type	`out-item-type`	Software Development	Out item types categorize out items.
Page Blueprint	`page-blueprint`	App	Document the purpose and usage of a page blueprint.
Page Blueprint Type	`page-blueprint-type`	App	Document the purpose and usage of the page blueprints of this type.
Pattern	`pattern`	Teamwork	Patterns provide solutions for problems in a given context. Patterns are usefull in multiple areas such as design, architecture, documentation, or process.
Pattern Domain	`pattern-domain`	Teamwork	Patterns are divided into different domains to group patterns.
Pattern Type	`pattern-type`	Teamwork	Categorize patterns by type.
Person	`person`	Core	Provides information about a person. This includes contact information (important if the person is relevant for the team) or information about the competences (if the person is an author about a topic relevant for the project).
Person Type	`person-type`	Core	Categorize persons by a type.
Problem	`problem`	Risk Management	Document problems as a means to communicate the details and to use the information for reviews and retrospections.
Problem Type	`problem-type`	Risk Management	Problems are grouped by their type.
Process Impact	`process-impact`	Service Management	Impacts define how the results of processes affect the world.
Process Impact Type	`process-impact-type`	Service Management	Type-specific category for impacts.
Process Outcome	`process-outcome`	Service Management	Outcomes define the results of processes.
Process Outcome Type	`process-outcome-type`	Service Management	Type-specific category for outcomes.
Product Backlog	`product-backlog`	Agile Team	Product Backlogs are means to collect user stories.
Profile	`profile`	Core	Profiles provide views on documents via delegation.
Profile Type	`profile-type`	Core	Categorize profiles by a type.
Project Constraint	`project-constraint`	Software Development	Project Constraints limit the options of a project.
Project Constraint Type	`project-constraint-type`	Software Development	Project constraint types categorize project constraints.
Project Rule	`project-rule`	Teamwork	Project Rules are defined by the team to enhance the collaboration and to define project standards.
Project Rule Type	`project-rule-type`	Teamwork	Categorize project rules by type.
Project Vision	`project vision`	Software Development	Frame the vision for a project or iteration.
Project Vision Type	`project-vision-type`	Software Development	Types to categorize vision statements for projects.
Property	`property`	Software Development	Properties are part of the configuration options of a system.
Property Type	`property-type`	Software Development	Property types categorize properties of products, such as parameters or configuration options.
Quality	`quality`	Software Development	Qualities describe desired aspects of the product.
Quality Scenario	`quality-scenario`	Software Development	Quality Scenarios document required qualities.
Quality Scenario Type	`quality-scenario-type`	Software Development	Quality scenario types categorize quality scenarios.
Quality Target	`quality-target`	Software Development	Documents a quality target for a product.
Quality Target Type	`quality-target-type`	Software Development	Group quality targets by their type.
Quote	`quote`	Core	Quotes relevant for the project. Allows to store the content and metadata to the quote.
Quote Type	`quote-type`	Core	Categorize quotes by a type.
Relation	`relation`	Core	Organizes glossary items.
Relation Type	`relation-type`	Core	Categorize relations by a type.
Release	`release`	Service Management	Releases document the changes that are applied to a published version of a service.
Release Note	`release-note`	Project Management	Document changes provided by a release of a product.
Release Note Type	`release-note-type`	Project Management	Group your release notes by a self-defined type.
Release Type	`release-type`	Service Management	Type-specific category for releases.
Report	`report`	Project Management	Reports document what the team has decided or done. This is a generic document.
Report Type	`report-type`	Project Management	Group your reports by a self-defined type.
Requirement	`requirement`	Software Development	Documents requirements of a product.
Requirement Type	`requirement-type`	Software Development	Categorization of requirements for a product.
Resource	`resource`	Core	Resources are books, webpages, videocasts relevant for the project. Add important information to your project about resources that lie outside the control of your team.
Resource Type	`resource-type`	Core	Resources are identified by their type. This is not the MIME type, but human readable string, that identifies the semantic, rather than the syntactic format.
Retrospective	`retrospective`	Agile Team	Record the discussion of the team about their last iteration.
Review	`review`	Agile Team	Plan and run your review meeting.
Review Act	`review-act`	Agile Team	A single act to show on the review. Use this only if you have a lot to show or you want to reference the review results later. Often a simple numerated list is sufficient.
Risk	`risk`	Risk Management	Document and track identified risks for the project.
Risk Action	`risk-action`	Risk Management	Document actions to prevent or reduce the negative impact on exceptions on a project.
Risk Action Type	`risk-action-type`	Risk Management	Risk actions are grouped by their type.
Risk Phase	`risk-phase`	Risk Management	Risks are grouped by the phase of their impact on the project.
Risk Probability	`risk-probability`	Risk Management	Risks are grouped by the probability of having impact on the project.
Risk Severity	`risk-severity`	Risk Management	Risks are grouped by the severity of their impact on the project.
Risk Target	`risk-target`	Risk Management	Document targets of risks.
Risk Target Type	`risk-target-type`	Risk Management	Risk tagets are grouped by their type.
Risk Type	`risk-type`	Risk Management	Risks are grouped by their type.
Role	`role`	Core	Defines a role with its responsibilities, tasks and requirements. Roles are incorporated by stakeholders who take interest in the project. The are also used to define the audience for documents.
Role Type	`role-type`	Core	Categorize roles by a type.
Section	`section`	Core	Sections of a document are typically part of a document. But the size of sections may vary. To support a team to write collaboratively on the documentation, a larger document may be subdivided into external section documents.
Section Type	`section-type`	Core	Categorize sections by a type.
Service Announcement	`service-announcement`	Service Management	Announcements communicate with stakeholders information about a service.
Service Announcement Type	`service-announcement-type`	Service Management	Type-specific category for service announcements.
Service Level	`service-level`	Service Management	Describe a service level for a service.
Service Level Agreement	`service-level-agreement`	Service Management	Provide information about a service level agreement (SLA).
Service Level Agreement Type	`service-level-agreement-type`	Service Management	Type-specific category for service level agreements.
Service Level Requirement	`service-level-requirement`	Service Management	Describe a requirement in terms of a service level.
Service Level Requirement Type	`service-level-requirement-type`	Service Management	Type-specific category for service level requirements.
Service Level Type	`service-level-type`	Service Management	Type-specific category for service levels.
Space Blueprint	`space-blueprint`	App	Document the purpose and usage of a space blueprint.
Space Blueprint Type	`space-blueprint-type`	App	Document the purpose and usage of the space blueprints of this type.
Space Index	`docsection`	Core	Compile other documents, yet space indices are themselves projectdoc documents. So they can be tagged and grouped.
Space Index Type	`space-index-type`	Core	Categorize space indexes by a type.
Space Property	`space-property`	App	Space properties hold metadata of a space. They may be inherited by delegate spaces.
Space Property Type	`space-property-type`	App	Document the purpose and usage of the space properties of this type.
Stakeholder	`stakeholder`	Core	A party that takes interest in a project. The stakeholder is either a real person, an organization or group, or represents a class of individuals, groups or organizations.
Stakeholder Type	`stakeholder-type`	Core	Categorize stakeholders by a type.
Step	`step`	Core	Describes a single step of an activity. A step is a generic document that is associated with a document that describes a process. It may be a test log or a howto.
Step Type	`step-type`	Core	Categorize steps by a type.
Strategy	`strategy`	Business Strategy	Defines a strategy for an organization or product.
Strategy Type	`strategy-type`	Business Strategy	Type-specific category for strategies.
Subject	`subject`	Core	Subject documents allow to set document instance of different doctypes in a common context.
Subject Type	`subject-type`	Core	Categorize subjects by a type.
SWOT	`swot`	Business Strategy	Work on strengths, weaknesses, opportunities, and threats.
SWOT Type	`swot-type`	Business Strategy	Type-specific category for SWOTs.
Tag	`tag`	Core	Document the semantics of a tag. May also be used to document Confluence labels.
Tag Type	`tag-type`	Core	Categorize tags by a type.
Team Process	`team-process`	Teamwork	Document processes defined and used by the team.
Team Process Type	`team-process-type`	Teamwork	Categorize team processes by type.
Technical Debt	`technical-debt`	Software Development	Technical Debts track issues to be paid back.
Technical Debt Type	`technical-debt-type`	Software Development	Technical Debts are grouped by the area they address.
Test Case	`test-case`	Software Development	Document a test case of your project.
Test Case Type	`test-case-type`	Software Development	Test case types categorize test cases.
Test Charter	`test-charter`	Software Development	Defines a charter to run an exploratory test session.
Test Charter Type	`test-charter-type`	Software Development	Test charter types categorize test charters.
Test Data	`test-data`	Software Development	Document data used for test cases.
Test Data Type	`test-data-type`	Software Development	Test data types categorize test data.
Test Report	`test-report`	Software Development	Documents the results of a test session for the sponsoring stakeholders.
Test Report Type	`test-report-type`	Software Development	Test report types categorize test reports.
Test Session	`test-session`	Software Development	Defines a document to collect information during a test session.
Test Session Type	`test-session-type`	Software Development	Test session types categorize test sessions.
Todo	`todo`	Developer Diaries	Add a todo note to your developer diary.
Todo Type	`todo-type`	Developer Diaries	Categories for todos.
Tool	`tool`	Teamwork	Document tools used by the team. Add information about how to fetch, install and best practices using it.
Tool Type	`tool-type`	Teamwork	Categorize tools by type.
Topic	`topic`	Core	A description of a given topic. A topic may describing or explaining a concept, a task to accomplish or a reference. There are a couple of topic types that set the expectations for the reader. Instances of the topic doctype usually have independent lifetimes from any referencing documents.
Topic Type	`topic-type`	Core	A topic type is a semantic type of the topic. It helps to set the expectations of potential readers.
Tour	`tour`	Core	Guided tours through existing information. This allows to aggregate topics for a given question or audience, thus providing a view on a topic.
Trigger	`trigger`	Service Management	Triggers define signals for activities and processes.
Trigger Type	`trigger-type`	Service Management	Type-specific category for triggers.
Use Case	`use-case`	Software Development	Defines a use case of the product.
Use Case Type	`use-case-type`	Software Development	Use case types categorize use cases.
User Character	`user-character`	Software Development	User Characters are the actors of user stories. They include personas and extreme characters.
User Character Type	`user-character-type`	Software Development	User character types categorize user characters.
User Story	`user-story`	Agile Team	User Stories document a requirement of a stakeholder with a specific business goal. It also provides an acceptance test. It is a representation of a unit of work.
Version	`version`	Core	Document a version of a product or service.
Version Type	`version-type`	Core	Categorize versions by a type.
View	`view`	Software Development	Different views on the product help to document the system and its architecture. Typical views are building block, runtime, or deployment.
View Type	`view-type`	Software Development	Groups the views at a system.
Vision	`vision`	Developer Diaries	Describe your vision for your career.
Vision Statement	`vision-statement`	Business Strategy	Define the vision for your organization or product.
Vision Statement Type	`vision-statement-type`	Business Strategy	Type-specific category for vision statements.
Vision Type	`vision-type`	Developer Diaries	Categories for visions.
Week	`week`	Developer Diaries	Plan and run a retrospective for your week of work.
Week Type	`week-type`	Developer Diaries	Categories for weeks.
Whitebox	`whitebox`	Software Development	Describe as a Whitebox the elements of a view where only the relations of internal elements are relevant.
Whitebox Type	`whitebox-type`	Software Development	Group whiteboxes by their type.
Work Instruction	`work-instruction`	Service Management	Work Instructions define procedures for processes. Provide the most detailed information here how tasks are to be executed. This includes best practices.
Work Instruction Type	`work-instruction-type`	Service Management	Type-specific category for work instructions.
Year	`year`	Developer Diaries	Create a year in your Diary.
Year Type	`year-type`	Developer Diaries	Categories for years.

Related Properties

Subject Home: A space property to control the location of the homepage of a given subject. Use the name of the subject to define the space property name. The value is a link to the page to store documents associated with the specified subject. Only available for versions prior to 2.0.

Doctype Home

Doctype Identifiers

Related Properties