projectdoc Toolbox

List of all doctypes provided by add-ons. Provides an overview over doctype IDs and blueprint keys.

Type: Reference

The list of doctypes available for projectdoc on this site.

The blueprint key is constructed by the blueprint key prefix defined by the add-on the doctype is part of and the doctype ID.

The blueprint key prefix for the projectdoc Developer Diaries is

de.smartics.atlassian.confluence.smartics-projectdoc-confluence-space-devdiary.projectdoc-blueprint-doctype-

The doctype ID for Event is event.

Therefore the blueprint key of the event doctype is

de.smartics.atlassian.confluence.smartics-projectdoc-confluence-space-devdiary.projectdoc-blueprint-doctype-event

The blueprint key prefixes for the add-ons are listed on the bottom of this page.

#	Name	ID	Set	Short Description
1	Access Information	`access-information`	Service Management	Credentials for development systems where the password is known to all who have access to the Confluence wiki.
2	Access Information Type	`access-information-type`	Service Management	Type-specific category for access information.
3	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.
4	Alternative Type	`alternative-type`	Project Management	Group your alternatives by a self-defined type.
5	Announcement	`announcement`	Agile Team	Announcements are a way to communicate an important piece of information with your team.
6	Annual Vision	`annual-vision`	Developer Diaries	Describe your vision for one year. You plan will help you stay focussed to accomplish your goals.
7	Annual Vision Type	`annual-vision-type`	Developer Diaries	Categories for annual visions.
8	App	`app`	App	Document your app for your users and customers.
9	App Component	`app-component`	App	Provide more detailed information about a component of a tool.
10	App Component Type	`app-component-type`	App	Document the purpose and usage of the components of this type.
11	App Extension	`app-extension`	App	Document your extension for your users and customers.
12	App Extension Type	`app-extension-type`	App	Document the purpose and usage of the extension of this type.
13	App Macro	`app-macro`	App	Document the purpose and usage of the macro.
14	App Macro Type	`app-macro-type`	App	Document the purpose and usage of the macros of this type.
15	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!
16	App Parameter Type	`app-parameter-type`	App	Document the purpose and usage of the app parameters of this type.
17	App Platform	`app-platform`	App	Document a platform for apps.
18	App Platform Type	`app-platform-type`	App	Document the purpose and usage of the platforms of this type.
19	App Service	`app-service`	App	Document a service provided by an app.
20	App Service Type	`app-service-type`	App	Document the purpose and usage of the app services of this type.
21	App Tool	`app-tool`	App	Document a tool provided by an app.
22	App Tool Type	`app-tool-type`	App	Document the purpose and usage of the app tools of this type.
23	App Type	`app-type`	App	Document the purpose and usage of the apps of this type.
24	Application	`application`	Service Management	Applications provided functions required by services. Applications may be hosted on one or more systems.
25	Application Type	`application-type`	Service Management	Type-specific category for applications.
26	arc42 Template	`swad`	arc42	The blueprint of the arc42 Template creates a tree of pages in the Confluence space.
27	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.
28	Architecture Alternative Type	`architecture-alternative-type`	Software Development	Group architecture alternatives by their type.
29	Architecture Aspect	`architecture-aspect`	Software Development	Document an aspect of your architecture. Something orthogonal or cross-functional like logging, exception handling or configurability.
30	Architecture Aspect Type	`architecture-aspect-type`	Software Development	Group architecture aspects by their type.
31	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.
32	Architecture Decision Type	`architecture-decision-type`	Software Development	Architecture decisions are group by their types. A commonly used decision type is 'Architecture'.
33	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.
34	Artifact Type	`artifact-type`	Software Development	Artifact types categorize artifacts.
35	Asset	`asset`	Developer Diaries	Explain an asset of your work. Add this document to a day in your diary.
36	Asset Type	`asset-type`	Developer Diaries	Categories for assets.
37	Association	`association`	Core	Associates two documents.
38	Association Type	`association-type`	Core	Categorize associations by a type.
39	Assumption	`assumption`	Risk Management	Document assumptions to assess risks and opportunities for the project.
40	Assumption	`assumption`		Assumptions document what you think about your product, customers, and partners. Once you start identifying assumptions, it will become clearer what other beliefs you hold about how you plan to build, design, distribute, and create value with your product. Making assumptions explicit allows to publish them and discuss them with other stakeholders.
41	Assumption Resolution	`assumption-resolution`		Assumptions can be resolved in different ways. Define what each resolution implies.
42	Assumption Resolution Type	`assumption-resolution-type`		Type-specific category for assumption resolutions.
43	Assumption Type	`assumption-type`	Risk Management	Assumptions are grouped by their type.
44	Assumption Type	`assumption-type`		Type-specific category for assumptions.
45	Blackbox	`blackbox`	Software Development	Describe as a Blackbox the elements of a view where only the externally visible properties are relevant.
46	Blackbox Type	`blackbox-type`	Software Development	Group blackboxes by their type.
47	Blank Document	`blank`	Native	The blank template simply provides a minimal integration with projectdoc features. It is a quick starting point to use projectdoc.
48	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.
49	Category	`category`	Core	Categories allow to set document instance of different doctypes in a hierarchy.
50	Category Type	`category-type`	Core	Categorize categories by a type.
51	Change	`change`	Service Management	Document a single change to configuration items or assets.
52	Change Severity	`change-severity`	Service Management	Add an severity to classify changes.
53	Change Status	`change-status`	Service Management	Add a status to categorize changes.
54	Change Theme	`change-theme`	Service Management	Add a theme to group changes.
55	Change Type	`change-type`	Service Management	Type-specific category for changes.
56	Charter	`charter`	Core	Describes an information need and use this description as a basis to create and maintain a document.
57	Charter Type	`charter-type`	Core	Categorize charters by a type.
58	Cheat	`cheat`	Developer Diaries	A brief solution to a problem.
59	Cheat Type	`cheat-type`	Developer Diaries	Categories for cheats.
60	Check-in	`okr-check-in`		Document the result of a OKR check-in.
61	Check-in Type	`okr-check-in-type`		Type-specific category for OKR check-ins.
62	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.
63	Checklist Type	`checklist-type`	Teamwork	Categorize checklists by type.
64	Code	`code`	Software Development	Describe the codes that are part of the product's API.
65	Code Type	`code-type`	Software Development	Code types categorize codes, used in logging or exception handling.
66	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.
67	Component Type	`component-type`	Software Development	Component types categorize components.
68	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.
69	Configuration Item Status	`configuration-item-status`	Service Management	Signals the status of an IT system, application, or a configuration item.
70	Configuration Item Type	`configuration-item-type`	Service Management	Type-specific category for configuration items.
71	Cycle	`cycle`	Core	Add cycles to group cycle phases.
72	Cycle Phase	`cycle-phase`	Core	Cycle phases define phases that are bound to a cycle, such as lifecycles or iterations.
73	Data Type	`datatype`		Document a data type for properties and codes.
74	Data Type Type	`datattype-type`	Software Development	Data type types categorize data types.
75	Dataset	`dataset`	Service Management	Datasets are used as the input and output of processes.
76	Dataset Type	`dataset-type`	Service Management	Type-specific category for datasets.
77	Day	`day`	Developer Diaries	Store relevant information discovered today in your developer diary.
78	Day Type	`day-type`	Developer Diaries	Categories for days.
79	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.
80	Decision Type	`decision-type`	Project Management	Group your decisions by a self-defined type.
81	Deployment	`deployment`	Service Management	Deployments provide information about updates on services and systems to users.
82	Deployment Record	`deployment-record`	Service Management	Record a deployment to a IT system.
83	Deployment Record Type	`change-type`	Service Management	Type-specific category for deployment records.
84	Deployment Type	`deployment-type`	Service Management	Type-specific category for deployments.
85	Diary	`diary`	Developer Diaries	The homepage of a developer's daily diary pages. Consider to add your diary to your personal space!
86	Diary Type	`diary-type`	Developer Diaries	Categories for diaries.
87	Doctype	`doctype`	App	Document the usage of a doctype for your users.
88	Doctype Type	`app-doctype-type`	App	Document the purpose and usage of the doctypes of this type.
89	Document Property	`document-property`	App	Document the usage of a document property for your users.
90	Document Property Type	`document-property-type`	App	Document the purpose and usage of the properties of this type.
91	Document Section	`document-section`	App	Document the usage of a document section for your users.
92	Document Section	`document-section-type`	App	Document the purpose and usage of the sections of this type.
93	Environment	`environment`	Software Development	Document logical or physical groups of nodes.
94	Environment Type	`environment-type`	Software Development	Type of an environment used by the project to deploy the application or the solution.
95	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.
96	Event Type	`event-type`	Developer Diaries	Categories for events.
97	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.
98	Excerpt Type	`excerpt-type`	Core	Categorize excerpts by a type.
99	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.
100	Experience Level Type	`experience-level-type`	Core	Categorize experience levels by a type.
101	FAQ	`faq`	Core	FAQs help to record an answer to a frequently asked question concerning the project, the product, the system or the process.
102	FAQ Type	`faq-type`	Core	Categorize FAQs by a type.
103	Feature	`feature`	Software Development	Documents a feature of the product. The top features define the main aspects of the product.
104	Feature Type	`feature-type`	Software Development	Feature types categorize features.
105	Generic	`generic`	Core	Generic Documents provide information where no other doctype matches.
106	Generic Type	`generic-type`	Core	Categorize generic documents by a type.
107	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.
108	Glossary Item Type	`glossary-item-type`	Core	Categorize glossary items by a type.
109	How	`map-how`		Describe how the impact will be pursued.
110	How Type	`map-how-type`		Type-specific category for hows.
111	Hypothesis	`hypothesis`		Write your problem hypothesis. This is the hypothesis that you will either validate or (probably) come back and revise.
112	Hypothesis Status	`hypothesis-type`		Type-specific category for hypotheses based on status.
113	Hypothesis Status Type	`hypothesis-status-type`		Type-specific category for hypothesis status.
114	Hypothesis Type	`hypothesis-type`		Type-specific category for hypotheses.
115	Impact	`impact`		Publish an impact you want to achieve. Share this information with your colleagues.
116	Impact Map	`impact-map`		Publish impacts you want to achieve. Share this information with your colleagues.
117	Impact Map Type	`impact-map-type`		Type-specific category for impact maps.
118	Impact Type	`impact-type`		Type-specific category for impacts.
119	Improvement	`improvement`	Agile Team	Improvement proposals help to start the conversation within the team for process improvements.
120	Interface	`interface`	Software Development	Interfaces document how elements of the system communicate with elements of this and other systems.
121	Interface Type	`interface-type`	Software Development	Group interfaces by their type.
122	IT Activity	`it-activity`	Service Management	IT Activities define activities for processes.
123	IT Activity Type	`it-activity-type`	Service Management	Type-specific category for IT activities.
124	IT Asset	`it-asset`	Service Management	IT Assets define assets required or produced by processes.
125	IT Asset Type	`it-asset-type`	Service Management	Type-specific category for IT assets.
126	IT Function	`it-function`	Service Management	Functions are specialized organizational units to support business processes.
127	IT Function Type	`it-function-type`	Service Management	Type-specific category for IT functions.
128	IT Procedure	`it-procedure`	Service Management	IT Procedures define procedures for processes.
129	IT Procedure Type	`it-procedure-type`	Service Management	Type-specific category for IT procedures.
130	IT Process	`it-process`	Service Management	Processes organize activities to create a defined business value.
131	IT Process Type	`it-process-type`	Service Management	Type-specific category for IT processes.
132	IT Service	`it-service`	Service Management	IT Services provide business relevant services for customers.
133	IT Service Classification	`it-service-classification`	Service Management	Classifiers to categorize services.
134	IT Service Classification Type	`it-service-classification-type`	Service Management	Type-specific classification for IT services.
135	IT Service Status	`it-service-status`	Service Management	Signals the status of an IT Service.
136	IT Service Type	`it-service-type`	Service Management	Type-specific category for IT services.
137	IT System	`it-system`	Service Management	Systems are part of environments where products are deployed to.
138	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.
139	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.
140	Key Result	`key-result`		Publish key results to achieve in order to pursue an objective to share with your colleagues.
141	Key Result Type	`key-result-type`		Type-specific category for key results.
142	Lifecycle	`lifecycle`	Service Management	Add lifecycles to group lifecycle phases.
143	Lifecycle Phase	`lifecycle-phase`	Service Management	Lifecycle phases define phases that are bound to a lifecycle.
144	Location	`location`	Service Management	Locations provide information about the whereabouts of assets, configuration items, and systems.
145	Location Type	`location-type`	Service Management	Type-specific category for locations.
146	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.
147	Media Type Type	`mediatype-type`	Core	Categorize media types by their type.
148	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.
149	Metadata Type	`metadata-type`	Core	Categorize metadata documents by a type.
150	Minutes	`minutes`	Project Management	Record the action items of a meeting.
151	Minutes Type	`minutes-type`	Project Management	Group your minutes by a self-defined type.
152	Mission Statement	`mission-statement`	Business Strategy	Define a mission for your company or product.
153	Mission Statement Type	`mission-statement-type`	Business Strategy	Type-specific category for mission statements.
154	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.
155	Module Type	`module-type`	Core	Categorization of document modules for single sourcing.
156	Month	`month`	Developer Diaries	Plan and run a retrospective for your month of work.
157	Month Type	`month-type`	Developer Diaries	Categories for months.
158	Node	`node`	Software Development	Nodes are part of environments where artifacts are deployed to.
159	Node Type	`node-type`	Software Development	Node types categorize nodes.
160	Objective	`objective`		Publish an objective to share with your colleagues.
161	Objective Type	`objective-type`		Type-specific category for objectives.
162	OKR Priority	`okr-priority`		Category to organize strategic themes, objectives, and key results.
163	Open Issue	`open-issue`	Project Management	Open issues document what the team needs to know to proceed.
164	Open Issue Severity	`open-issue-severity`	Project Management	Open issues are grouped by the severity of their impact on the project.
165	Open Issue Status	`open-issue-status`	Project Management	Open issues are grouped by the status.
166	Open Issue Type	`open-issue-type`	Project Management	Group your open issues by a self-defined type.
167	Opportunity	`opportunity`	Risk Management	Document and track identified opportunities for the project.
168	Opportunity Type	`opportunity-type`	Risk Management	Opportunities are grouped by their type.
169	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.
170	Organization Type	`organization-type`	Core	Categorize organizations by a type.
171	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.
172	Out Item Type	`out-item-type`	Software Development	Out item types categorize out items.
173	Outcome	`outcome`		Products used by customers intend to make a change. This change is called outcome.
174	Outcome Type	`outcome-type`		Type-specific category for outcomes.
175	Output	`output`		The output is the artifact created to be employed by user for a specific outcome and - on the long run - may make an impact.
176	Output Type	`output-type`		Type-specific category for outputs.
177	Page Blueprint	`page-blueprint`	App	Document the purpose and usage of a page blueprint.
178	Page Blueprint Type	`page-blueprint-type`	App	Document the purpose and usage of the page blueprints of this type.
179	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.
180	Pattern Domain	`pattern-domain`	Teamwork	Patterns are divided into different domains to group patterns.
181	Pattern Type	`pattern-type`	Teamwork	Categorize patterns by type.
182	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).
183	Person Type	`person-type`	Core	Categorize persons by a type.
184	Problem	`problem`	Risk Management	Document problems as a means to communicate the details and to use the information for reviews and retrospections.
185	Problem Type	`problem-type`	Risk Management	Problems are grouped by their type.
186	Process Impact	`process-impact`	Service Management	Impacts define how the results of processes affect the world.
187	Process Impact Type	`process-impact-type`	Service Management	Type-specific category for impacts.
188	Process Outcome	`process-outcome`	Service Management	Outcomes define the results of processes.
189	Process Outcome Type	`process-outcome-type`	Service Management	Type-specific category for outcomes.
190	Product Backlog	`product-backlog`	Agile Team	Product Backlogs are means to collect user stories.
191	Profile	`profile`	Core	Profiles provide views on documents via delegation.
192	Profile Type	`profile-type`	Core	Categorize profiles by a type.
193	Project Constraint	`project-constraint`	Software Development	Project Constraints limit the options of a project.
194	Project Constraint Type	`project-constraint-type`	Software Development	Project constraint types categorize project constraints.
195	Project Rule	`project-rule`	Teamwork	Project Rules are defined by the team to enhance the collaboration and to define project standards.
196	Project Rule Type	`project-rule-type`	Teamwork	Categorize project rules by type.
197	Project Vision	`project vision`	Software Development	Frame the vision for a project or iteration.
198	Project Vision Type	`project-vision-type`	Software Development	Types to categorize vision statements for projects.
199	Property	`property`	Software Development	Properties are part of the configuration options of a system.
200	Property Type	`property-type`	Software Development	Property types categorize properties of products, such as parameters or configuration options.
201	Quality	`quality`	Software Development	Qualities describe desired aspects of the product.
202	Quality Scenario	`quality-scenario`	Software Development	Quality Scenarios document required qualities.
203	Quality Scenario Type	`quality-scenario-type`	Software Development	Quality scenario types categorize quality scenarios.
204	Quality Target	`quality-target`	Software Development	Documents a quality target for a product.
205	Quality Target Type	`quality-target-type`	Software Development	Group quality targets by their type.
206	Quote	`quote`	Core	Quotes relevant for the project. Allows to store the content and metadata to the quote.
207	Quote Type	`quote-type`	Core	Categorize quotes by a type.
208	Relation	`relation`	Core	Organizes glossary items.
209	Relation Type	`relation-type`	Core	Categorize relations by a type.
210	Release	`release`	Service Management	Releases document the changes that are applied to a published version of a service.
211	Release Note	`release-note`	Project Management	Document changes provided by a release of a product.
212	Release Note Type	`release-note-type`	Project Management	Group your release notes by a self-defined type.
213	Release Type	`release-type`	Service Management	Type-specific category for releases.
214	Report	`report`	Project Management	Reports document what the team has decided or done. This is a generic document.
215	Report Type	`report-type`	Project Management	Group your reports by a self-defined type.
216	Requirement	`requirement`	Software Development	Documents requirements of a product.
217	Requirement Type	`requirement-type`	Software Development	Categorization of requirements for a product.
218	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.
219	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.
220	Retrospective	`retrospective`	Agile Team	Record the discussion of the team about their last iteration.
221	Review	`review`	Agile Team	Plan and run your review meeting.
222	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.
223	Risk	`risk`	Risk Management	Document and track identified risks for the project.
224	Risk Action	`risk-action`	Risk Management	Document actions to prevent or reduce the negative impact on exceptions on a project.
225	Risk Action Type	`risk-action-type`	Risk Management	Risk actions are grouped by their type.
226	Risk Phase	`risk-phase`	Risk Management	Risks are grouped by the phase of their impact on the project.
227	Risk Probability	`risk-probability`	Risk Management	Risks are grouped by the probability of having impact on the project.
228	Risk Severity	`risk-severity`	Risk Management	Risks are grouped by the severity of their impact on the project.
229	Risk Target	`risk-target`	Risk Management	Document targets of risks.
230	Risk Target Type	`risk-target-type`	Risk Management	Risk tagets are grouped by their type.
231	Risk Type	`risk-type`	Risk Management	Risks are grouped by their type.
232	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.
233	Role Type	`role-type`	Core	Categorize roles by a type.
234	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.
235	Section Type	`section-type`	Core	Categorize sections by a type.
236	Service Announcement	`service-announcement`	Service Management	Announcements communicate with stakeholders information about a service.
237	Service Announcement Type	`service-announcement-type`	Service Management	Type-specific category for service announcements.
238	Service Level	`service-level`	Service Management	Describe a service level for a service.
239	Service Level Agreement	`service-level-agreement`	Service Management	Provide information about a service level agreement (SLA).
240	Service Level Agreement Type	`service-level-agreement-type`	Service Management	Type-specific category for service level agreements.
241	Service Level Requirement	`service-level-requirement`	Service Management	Describe a requirement in terms of a service level.
242	Service Level Requirement Type	`service-level-requirement-type`	Service Management	Type-specific category for service level requirements.
243	Service Level Type	`service-level-type`	Service Management	Type-specific category for service levels.
244	Space Blueprint	`space-blueprint`	App	Document the purpose and usage of a space blueprint.
245	Space Blueprint Type	`space-blueprint-type`	App	Document the purpose and usage of the space blueprints of this type.
246	Space Index	`docsection`	Core	Compile other documents, yet space indices are themselves projectdoc documents. So they can be tagged and grouped.
247	Space Index Type	`space-index-type`	Core	Categorize space indexes by a type.
248	Space Property	`space-property`	App	Space properties hold metadata of a space. They may be inherited by delegate spaces.
249	Space Property Type	`space-property-type`	App	Document the purpose and usage of the space properties of this type.
250	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.
251	Stakeholder Type	`stakeholder-type`	Core	Categorize stakeholders by a type.
252	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.
253	Step Type	`step-type`	Core	Categorize steps by a type.
254	Strategic Theme	`strategic-theme`		Publish a strategic theme to group objectives and to share them with your colleagues.
255	Strategic Theme Type	`strategic-theme-type`		Type-specific category for strategic themes.
256	Strategy	`strategy`	Business Strategy	Defines a strategy for an organization or product.
257	Strategy Type	`strategy-type`	Business Strategy	Type-specific category for strategies.
258	Subject	`subject`	Core	Subject documents allow to set document instance of different doctypes in a common context.
259	Subject Type	`subject-type`	Core	Categorize subjects by a type.
260	SWOT	`swot`	Business Strategy	Work on strengths, weaknesses, opportunities, and threats.
261	SWOT Type	`swot-type`	Business Strategy	Type-specific category for SWOTs.
262	Tag	`tag`	Core	Document the semantics of a tag. May also be used to document Confluence labels.
263	Tag Type	`tag-type`	Core	Categorize tags by a type.
264	Team Process	`team-process`	Teamwork	Document processes defined and used by the team.
265	Team Process Type	`team-process-type`	Teamwork	Categorize team processes by type.
266	Technical Debt	`technical-debt`	Software Development	Technical Debts track issues to be paid back.
267	Technical Debt Type	`technical-debt-type`	Software Development	Technical Debts are grouped by the area they address.
268	Test Case	`test-case`	Software Development	Document a test case of your project.
269	Test Case Type	`test-case-type`	Software Development	Test case types categorize test cases.
270	Test Charter	`test-charter`	Software Development	Defines a charter to run an exploratory test session.
271	Test Charter Type	`test-charter-type`	Software Development	Test charter types categorize test charters.
272	Test Data	`test-data`	Software Development	Document data used for test cases.
273	Test Data Type	`test-data-type`	Software Development	Test data types categorize test data.
274	Test Report	`test-report`	Software Development	Documents the results of a test session for the sponsoring stakeholders.
275	Test Report Type	`test-report-type`	Software Development	Test report types categorize test reports.
276	Test Session	`test-session`	Software Development	Defines a document to collect information during a test session.
277	Test Session Type	`test-session-type`	Software Development	Test session types categorize test sessions.
278	Todo	`todo`	Developer Diaries	Add a todo note to your developer diary.
279	Todo Type	`todo-type`	Developer Diaries	Categories for todos.
280	Tool	`tool`	Teamwork	Document tools used by the team. Add information about how to fetch, install and best practices using it.
281	Tool Type	`tool-type`	Teamwork	Categorize tools by type.
282	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.
283	Topic Type	`topic-type`	Core	A topic type is a semantic type of the topic. It helps to set the expectations of potential readers.
284	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.
285	Trigger	`trigger`	Service Management	Triggers define signals for activities and processes.
286	Trigger Type	`trigger-type`	Service Management	Type-specific category for triggers.
287	Use Case	`use-case`	Software Development	Defines a use case of the product.
288	Use Case Type	`use-case-type`	Software Development	Use case types categorize use cases.
289	User Character	`user-character`	Software Development	User Characters are the actors of user stories. They include personas and extreme characters.
290	User Character Type	`user-character-type`	Software Development	User character types categorize user characters.
291	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.
292	Version	`version`	Core	Document a version of a product or service.
293	Version Type	`version-type`	Core	Categorize versions by a type.
294	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.
295	View Type	`view-type`	Software Development	Groups the views at a system.
296	Vision	`vision`	Developer Diaries	Describe your vision for your career.
297	Vision Statement	`vision-statement`	Business Strategy	Define the vision for your organization or product.
298	Vision Statement Type	`vision-statement-type`	Business Strategy	Type-specific category for vision statements.
299	Vision Type	`vision-type`	Developer Diaries	Categories for visions.
300	Week	`week`	Developer Diaries	Plan and run a retrospective for your week of work.
301	Week Type	`week-type`	Developer Diaries	Categories for weeks.
302	What	`map-what`		Describe the (high-level) deliverables (aka outcomes and outputs) required to achieve the impact.
303	What Type	`map-what-type`		Type-specific category for whats.
304	Whitebox	`whitebox`	Software Development	Describe as a Whitebox the elements of a view where only the relations of internal elements are relevant.
305	Whitebox Type	`whitebox-type`	Software Development	Group whiteboxes by their type.
306	Who	`map-who`		Describe who is involved in the impact. List the stakeholders that will support the impact. There may be stakeholders who will work against it. Also specify the stakeholders taking advantage or taking disadvantage even if they do not have power to influence the outcome.
307	Who Type	`map-who-type`		Type-specific category for whos.
308	Why	`map-why`		Describe why this impact is useful for your business. State the problem to be solved.
309	Why Type	`map-why-type`		Type-specific category for whys.
310	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.
311	Work Instruction Type	`work-instruction-type`	Service Management	Type-specific category for work instructions.
312	Wrap-up	`okr-wrap-up`		Track what you have achieved and the reasons why. Check what you have learned and find areas where you can improve.
313	Wrap-up Type	`okr-wrap-up-type`		Type-specific category for OKR wrap-ups.
314	Year	`year`	Developer Diaries	Create a year in your Diary.
315	Year Type	`year-type`	Developer Diaries	Categories for years.

Set names that are not rendered as links are not yet published.

Blueprint Key Prefixes by Add-on

The set named 'Native' refers to doctypes provided by the projectdoc Toolbox – which is actually only one doctype Blank Document Doctype.

Name	Set	Blueprint Key Prefix
Doctypes for Agile Planning	Agile Team	`de.smartics.atlassian.confluence.smartics-projectdoc-confluence-space-agileplanning:projectdoc-blueprint-doctype-`
projectdoc Add-on for arc42	arc42	`de.smartics.atlassian.confluence.smartics-projectdoc-confluence-arc42:projectdoc-arc42-blueprint-doctype-`
Core Doctypes	Core	`de.smartics.atlassian.confluence.smartics-projectdoc-confluence-space-core:projectdoc-blueprint-doctype-`
projectdoc Developer Diaries	Developer Diaries	`de.smartics.atlassian.confluence.smartics-projectdoc-confluence-space-devdiary.projectdoc-blueprint-doctype-`
Doctypes	Native	`de.smartics.atlassian.confluence.smartics-projectdoc-confluence:projectdoc-blueprint-doctype-`
Doctypes for Project Management	Project Management	`de.smartics.atlassian.confluence.smartics-projectdoc-confluence-space-prjmgmt:projectdoc-blueprint-doctype-`
Doctypes for Risk Management	Risk Management	`de.smartics.atlassian.confluence.smartics-projectdoc-confluence-space-riskmgmt:projectdoc-blueprint-doctype-`
Doctypes for Software Development	Software Development	`de.smartics.atlassian.confluence.smartics-projectdoc-confluence-space-swdev:projectdoc-blueprint-doctype-`

Doctype add-ons are available on the Atlassian Marketplace and on Bitbucket.

Space shortcuts

Page tree

Docs

Support

Free Blueprints

Tooling for Blueprints

Free Extensions

Spaces

Plugins for Maven

Incubator

Libraries for Java

Incubator

Add-ons for Confluence

Tools

Support

Team

Legal

Blueprint Key Prefixes by Add-on

About

Keep up-to-date!

Powered by