Example: Creating a Jira Service Desk internal comment on linked issues
Is this possible?: Writing to or reading from linked issues we need to set a new comment in a Service Desk project, but the comment has to be "Internal". At the moment, new comments are shared with the customer.
We can use post-functions Write field on linked issues or subtasks or Update issue fields selecting "New comment" or "New comment (sends email notifications)" as target field, for creating comments on linked issues, sub-tasks, or any issue selections by JQL or issue list expression. Comments created by this procedure will not have any visibility restriction, but we can limit the visibility by making our comments end in ": {visibility=visibility_value}", with visibility_value being a project role name a group name, "jsd_internal" or "jsd_public", as explained at: Add a comment.
Let's say we want to add an internal comment in all tasks of an Epic issue. In this case we use the post function Update issue fields:
Text to be parsed is: This is an internal comment created by the Epic issue.: {visibility=jsd_internal}
Other examples of that functions
Write field on linked issues or sub-tasks
- Add and remove a single or a set of items from multi valued fields
- Automatically become watcher of every issue blocking an issue assigned to you
- Automatically close resolved sub-tasks when parent issue is closed
- Automatically resolve an epic when all its stories are resolved
- Compose dynamic text by inserting field values in a text template
- Copy "Due date" into a date type custom field in a linked issue if it's greater than current issue's "Due date"
- Copy attachments from one issue to another
- Create a comment in sub-tasks when parent transitions
- Creating a Jira Service Desk internal comment
- Creating a Jira Service Desk internal comment on linked issues
- Execute transition in epic
- Make linked issues, sub-tasks and JQL selected issues progress through its workflows
- Moving sub-tasks to "Open" status when parent issue moves to "In Progress"
- Sum sub-task's "Time Spent" (work logs) and add it to a certain linked issue
- Transition sub-tasks when parent is transitioned
Write field on issues returned by JQL Query or Issue List
- Add and remove a single or a set of items from multi valued fields
- Compose dynamic text by inserting field values in a text template
- Creating a Jira Service Desk internal comment
- Creating a Jira Service Desk internal comment on linked issues
- Make linked issues, sub-tasks and JQL selected issues progress through its workflows
- Moving sub-tasks to "Open" status when parent issue moves to "In Progress"
- Parse Email adresses to watchers list
- Set priority for issues that have been in a certain status for longer than 24 hours
- Transition linked issues in currently active sprint
- Transition only a sub-task among several ones
- Using project properties to calculate custom sequence numbers
- Writing a comment to blocked issues when blocking issues are resolved