@@ -414,8 +414,10 @@ operation on ``https://.../rest/data/issue``.
414414 warnings about this below. Using this for collections is
415415 discouraged as it is slow and produces a lot of data.
416416 * - ``@fields=status,title``
417- - will return the ``status`` and ``title`` fields for the issue displayed
418- according to the @verbose parameter
417+ - will return the ``status`` and ``title`` fields for the
418+ displayed issues. It is added to the fields returned by the
419+ @verbose parameter. Protected properties
420+ can be included in the list and will be returned.
419421
420422In addition collections support the ``@fields`` parameter which is a
421423colon or comma separated list of fields to embed in the response. For
@@ -642,7 +644,13 @@ By default all (visible to the current user) attributes/properties are
642644returned. You can limit this by using the ``@fields`` query parameter
643645similar to how it is used in collections. This way you can only return
644646the fields you are interested in reducing network load as well as
645- memory and parsing time on the client side.
647+ memory and parsing time on the client side. By default protected
648+ properties (read only in the database) are not listed. Th
649+ is makes it easier to submit the attributes from a
650+ ``@verbose=0`` query using PUT. To include protected properties
651+ in the output og a GET add the query parameter
652+ ``@protected=true`` to the query and attributes like: actor,
653+ created, creator and activity will be include in the result.
646654
647655Link and Multilink properties are displayed as a dictionary with a
648656``link`` and an ``id`` property by default. This is controlled by the
0 commit comments