Features used to implement the example
- Write field on linked issues or sub-tasks
- Virtual field "New watchers"
Example: Automatically become watcher of every issue blocking an issue assigned to you
We may be interested in automatically making an assignee watcher of every issue blocking the current issue, in order to react as soon as possible to any change in those issues. Post-function Write field on linked issues or sub-tasks is used to write the name or current issue's assignee into the virtual field "New watchers" of those issues linked with current issue using a "is blocked by" issue link. We will also become watcher of every issue transitively blocking our issue, i.e., any issue blocking another issue which is itself blocking current issue.
ISSUE A --blocks--> ISSUE B --blocks--> ISSUE C --blocks--> ISSUE D, in this example issue A is blocking directly issue B and transitively issue C and D. To implement this behavior we simply have to check option "Write linked issues and sub-tasks recursively" in post-function Write field on linked issues or sub-tasks.
We use post-function Write field on linked issues or sub-tasks to write field "Assignee" into virtual field "New watchers" in all blocking issues:
Once configured, the transition will look like this:
Other examples of that function
- 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
