Allow to set placeholders to be replaced with space (and page) properties. Currently only a handful of @-marked placeholders are considered. Replace any placeholder defined with ${...}.

This will also help to reference versioned documents.

The description is a descriptive abstract to introduce the reader in the structure of the document. It is used to help readers to determine whether or not the document at hand is interesting for their problem or not.

We also want a section to contain the informative abstract. Readers may read this summary and get all information of the document in a brief manner.

Team could therefore define the structure of the document in the description and collect information in the summary. This will support collaboration.

Not all document types need a summary. Categories, Tags, ... have descriptions and that is all they need. But each document with a topic-like intention should have a section called summary to host informative information.

To make the last update of a transcluded fragment visible to authors, render the timestamp of the last update on the box around the transcluded content.

Allow to add a space description on creating a space with a wizard.

For later reference store the version document instance in the blueprint context by the key "projectdoc.pages.version". This will allow report generators to attach themselves to that version.

Allow to select the icon to be rendered as in a column of the space list rendered by the Space List Macro.

Like the Name List Macros the Parent Property Macro should also support ancestor searches.

The semantics of transclusions should be improved to:

• a suppressed section suppresses all subsections
• a suppressed section will also be suppressed as subsection
• transcluded content on a transcluded page is untouched by the selection

All Create-Buttons have to be hidden if the user has only reading privileges.

Some templates already have this guard, but now we want all templates to provide it.

The Quote Macro renders the "Publication Date" property of a document instance. If this is not specified, it should render a generic "Date" property.

The document properties on the blank template should not override the standard settings of the space.

'Blank Space' is misleading. We provide this space blueprint to get new users start with projectdoc quickly. The main aspect of the space is that it does not assume that users employ any document types (not even the core doctypes!). Therefore the Tags and Categories properties do not assume the use of the Tag and Category doctype and do not render a Name List Macro.

We should get this message more clear on the Space and Page Blueprint and rename the Space to 'Starter Space'. The name 'Blank Page' seems good enough. It is basically a blank page in the sense of projectdoc. If users would use the Core Doctypes they would use the Generic Doctype which integrates with the other Core Doctypes (e.g. Role, Tag, and Category).

Add a parameter to suppress the table header.

As a workaround run a refresh on the generated page tree whenever we create one.

It seems that the API we generate page by page does not work as expected. Sometimes we do not get properly created pages. At least they seem to pass the Lucene Indexer to late.

We should check if we could alter the use case to get a more performant solution.

If the Section Macro contains media content, it does not render. This is because it regards the iframes used by Confluence to render media as empty.

We should check for iframes and assume that they are not empty to render sections that contain only a reference (via an iframe) to media content.

Add documentation to the Sort By Property of Display Table, Display List, and Transclude Documents Macro. The Type Conversion feature is not obvious.

The message of the Nexus Link Macro for signalling errors to the user is rather brief. We should add a link to the documentation to help users finding out what to do more quickly.

Add spacekey to tooltip in link of transclusion box to transcluded page.

On starting the tree refresh action the browser reports a content encoding problem.

Transclusion parsed the content and thereby translates CDATA content to text.

See https://github.com/jhy/jsoup/issues/406.

We have to preserve the CDATA block otherwise the code macro will not render the content correctly.

The cache that stores the doctype information gets lost. This is okay, since it is a cache, but currently it is not able to refill itself.

The consequence is that ancestor searches (those based on the type of a property) will not work. The failure is an empty result set.

In any situation that invalidates the cache or its contents (low memory, restarts, redeployments, ...) the cache is required to get back to a valid state.

If a value to query for in an exact match query contains a special character (e.g. a bracket), the query parser is unable to parse the input string successfully. The problem is that the user has to have the option to escape characters that have to be taken verbatim. The parser cannot, without any help, examine the input string and detect which spacial characters are taken as is and which have special meaning.

We therefore need the feature of escaping characters.

For instance: To find a document with an exact match containing brackets, the query looks like this:

$<Identifier>=[My Term (with brackets)]

The information for new users to get started with projectdoc has a link that points to a non-existing page.

It should link to www.smartics.eu/confluence/display/PDAC1/projectdoc+for+Confluence+V1

Activating the Counter Column in a Display Table Macro and using the Calculate Columns feature leads to a corrupt rendering of the table.

The display list renders the normalized original value instead of the normalized rendered value.

Setting the "Name as Heading" property of the Transclude Documents Macro will render the title of the document as heading twice, if there are properties selected. The Select property contains "Name, Iteration". No Ids or Tags selected.

The rendering of the second heading should check if a heading is already rendered and suppress the duplicate rendering.

In addition to that the level of the transcluded sections have to be increased by one level if the heading is rendered in front of the properties table.

If the tour macro contains a link to a page the user has not access to, the whole table is not rendered.

Instead only the links to the page without access permissions should be skipped.

The remove-Create-Template-Button feature does not remove the element any longer. This problem applies to the latest Confluence version (5.8.9).

When box macros are stacked the inner boxes are rendered with wrong images.