Confluence rest api documentation defines as : "Content properties are a key / value store of properties attached to a piece of Content. The key is a string, and the value is a JSON object."
Confluence developer documentation defines as : "Content properties are a key-value storage associated with a piece of Confluence content, and are one of the forms of persistence available to you as an add-on developer. Content properties free you from having to use your own data store, by allowing you to store up to 32KB of JSON with each piece of content (a page, blog post, or an attachment). If you need to store metadata about a piece (or pieces) of content, for example, this is a great way to do it."
Confluence properties macro defintion defines as: "The Page Properties and Page Properties Report macro work together to enable you to show summary information from one page on a another page. You can see examples of these two macros in action on the Decision and Product Requirements blueprints."
However, the macro and rest api, although they both use the same jargon of property, their meaning are probably not same. Because there properties created by Rest api can not be bess by Property Report macro, and vice versa, the property macro can not be seen by REST api Property call.
Is it so?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.