Add watchers to related issues

Created by Marcin Żurawiecki
Nov 03, 2020

Overview

The Add watchers to related issues post function allows you to add users to or overwrite the watcher list with a user (or users) set in a User Picker custom field or defined explicitly to sub-task, parent, or linked issues when a workflow transition is executed.

Configuration

  1. Select the relation type in the Perform action on field to decide if the users will be added to (or overwrite) the watcher list on sub-task, parent, or linked issues

    1. If Parent or Sub-tasks was selected, set the Applies to field to decide if the users will be added to (or overwrite) the watcher list on issues with any or selected issue type. If Selected was set, choose the issue types in case of which the users will be added to (or overwrite) the watcher list in the Issue types field

    2. If Linked was selected, set the Applies to field to decide if the users will be added to (or overwrite) the watcher list on issues linked with any or selected issue link. If Selected was set, define the details of the issue link used to link issues to whose watcher list the users will be added (or will overwrite it):

      1. Set the type of link in the Link type field

      2. Set the direction of link in the Link direction field

  2. Select if the users should be added to the watcher list or overwrite the list in the Operation type field

  3. Select a User Picker custom field (single or multiple users) from which users will be added to (or will overwrite) the watcher list in the User Picker custom field field

  4. Define the users that will be added to (or will overwrite) the watcher list explicitly in the Users field

  5. Select if the post function should be executed by the current or another user in the Action executor field (see User Permissions below)

    1. If you have selected Current user option, the post function will be executed by the user making the workflow transition

    2. If you have selected Another user option, provide a user in the User field, so that the post function will be executed by this user

  6. Activate the JQL condition option and define the JQL query that has to be met by the issue in order to execute the post function (e.g. “type = Bug and Priority = Blocker”)

  7. Activate the Executor condition option if you want the post function to be executed only if the user is or isn’t in a certain Jira user group or project role

    1. Select if The executor has to be or can’t be a member of a certain Jira user group or project role

      1. Select a Jira user group in the Group field if Group was set in the member of a field

      2. Select a project role in the Project role field if Project role was set in the member of a field

User Permissions

The user set as Action executor in point 5 needs to have the Browse Projects and Manage Watchers permissions in the project of the related issue in order to execute the post function.

Mandatory fields

At least one of the fields User Picker custom field and Users needs to be filled in. If both fields are not set, you will not be able to add the post function.

Use cases

  • Escalation of the issue in Jira Service Desk adds the project manager to the internal issue, that is linked to the JSD request

  • Escalation of the onboarding issue adds the supervisor to the sub-tasks that are still open and the onboarding is about to end