Support for providing properties by attached files, list documents by properties, and accessing ancestor properties
Today we released version 1.16.0 of the projectdoc Toolbox on the Atlassian Marketplace!
The projectdoc Toolbox is an add-on for Confluence supporting agile software development teams to collaborate on process, project, system, and product documentation.
If you want to learn more about the projectdoc Toolbox and how it helps to create good project documentation, please refer to the introduction video!
The following image is a link to a video on YouTube. When you click the link your browser will serve a page from youtube.com.
Very interesting, but way too fast?
Step through at your own pace with with our Prezi Presentation (external link to prezi.com)!
In the Online Manual you’ll find additional video material that introduces you in the concepts of the projectdoc Toolbox.
Refer to use cases and show cases for information on how to use the projectdoc Toolbox.
New and Noteworthy
The following changes may be the most interesting of this release.
Attached Properties
With PDAC-718 - Getting issue details... STATUS the projectdoc Toolbox allows to specify document properties as attachments to the Confluence page.
This enhancement makes it easier to add and updated exported properties from a system.
mail.imap.user=jane.doe mail.imap.host=mail.smartics.eu
Tour-by-Property
Program the table of documents by a document property with the Tour-by-Property Macro. The property lists references to documents.
The list may also be traversed breadth-first or depth-first to include information that is referenced by the processed documents.
List Ancestor Property
The Parent Property Macro renders a property from the parent document right from version one. The new Ancestor Property Macro now provides access to a property from the first ancestor document matching the specified document type.
In case you have a hierarchy of documents with different doctypes, you may access information from a specific doctype from all children. For instance if systems and subsystems are deployed in an environment then all the systems document can easily access information from the environment document, being the root of a tree of system documents.
