Page History
Page properties | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
|
Code Block | ||||
---|---|---|---|---|
| ||||
%{issue.lastComment.visibility} |
Read
Page properties | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
UI Text Box | ||
---|---|---|
| ||
This field can be used to check for visibility restrictions of the last comment. The output will be the group or project role the visibility of the last comment is restricted to. If no restriction is applied to the comment or there is no comment present yet, this this field returns an empty text. |
UI Text Box | ||
---|---|---|
| ||
For service projects, "Public" is returned for unrestricted (customer-visible) comments and "Internal" for internal (agent-only) onesFor Service Desk's special Internal visibility restriction, the text "Internal" is returned. |
Write
Page properties | ||||||
---|---|---|---|---|---|---|
| ||||||
|
UI Text Box | ||||||
---|---|---|---|---|---|---|
| ||||||
Updates the visibility of the last comment in the issue if it exists.:
|
UI Text Box | ||||||
---|---|---|---|---|---|---|
| ||||||
For service projects, "Public" and "Internal" In Jira Service Desk it also admits values public and internal (without double quotes) , or alternatively are available to control the visibililty among agents and customers. Alternatively, you can use jsd_public and jsd_internal to avoid name collision with existing project roles and user groups.
|
Page properties | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
Page properties | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
|