This post function allows users to add/remove watchers to/from the current, parent, selected or any issue returned by a parser expression.
You can retrieve the users from either an existing field, project role, or group.
⚒️ Configuration
Target issue
Select the issue to add or remove watchers. If a list of issue keys is passed, the function will be performed for every issue in the list.
The following options are available:
-
Current issue
-
Parent of current issue
-
Selected issue
-
Parser expression
When the option parser expression is selected, an expression parser input field is displayed and the input has to be an issue key or an issue list. The watchers will be added or removed to the issues specified by the given issue keys.
Mode
The mode parameter defines how you want to retrieve the users to be added or removed as watchers. The following modes are available:
|
Option |
Description |
|---|---|
|
Add users from a field |
You will be presented with a dynamic selection, containing available fields (or field codes) where the user(s) should be retrieved from. If you select a text field, the output must contain a single or comma separated list of Atlassian account Ids.
|
|
Add members of a project role |
You will be presented with a dynamic selection, containing available project roles. All users from the selected project role (in the current project) will be added as watchers.
|
|
Add members of a group |
You will be presented with a dynamic selection, containing available groups. All users from the selected group will be added as watchers.
|
|
Remove users from a field |
You will be presented with a dynamic selection, containing available fields (or field codes) where the user(s) should be retrieved from. If you select a text field, the output must contain a single or comma seperated list of Atlassian account lds.
|
|
Remove members of a project role |
You will be presented with a dynamic selection, containing available project roles. All users from the selected project role (in the current project) will be removed as watchers.
|
|
Remove members of a group |
You will be presented with a dynamic selection, containing available groups. All users from the selected group will be removed as watchers.
|
|
Remove all watchers |
Check this option to remove all watchers from the current issue. |
If you need to add or remove watchers from multiple groups or project roles, you need to configure additional post functions.
Run as
Select the user that will be used to execute the post function. By default, it is set to the current user that executes the transition.
The following options are available:
|
Option |
Description |
|---|---|
|
Selected user |
Select a specific Jira user. |
|
User in field |
Select the field containing the user that will be used to execute the post function. |
The configured user must have all necessary permissions to add or remove watchers in the target issue.
Conditional execution
You can optionally specify a logical expression or a Jira expression depending on the chosen Parsing mode to define the circumstances (or conditions) under which the post function should be executed.
The result of the logical expression must return a boolean value of either:
-
true→ the post function will be executed -
false→ the post function will not be executed
Using the conditional operator, even complex or multi-layered conditions can be constructed.
Make sure to learn more about defining logical expressions and browse through the various examples here: Logical mode
📚 Use cases and examples
| Use case | JWT feature | Workflow function | Use case description | Complexity |
|---|---|---|---|---|
| Deleting watchers from rejected incidents |
|
Add or remove watchers | After an incident is rejected, the functionality automatically removes all watchers from the issue. This guarantees that no other people remain in the information loop for the rejected issue, streamlining communication and focusing on active incidents. | |
| Keep the project lead informed of any new issues |
|
Add or remove watchers | Anytime a new issue is created in the "Project Management" Jira project, the functionality automatically adds the project lead as an observer. The project lead is thereby kept up to date with all new updates and information within the project, facilitating effective monitoring and management. | |
| Keeping developers informed about new software requirements |
|
Add or remove watchers | Each time a new software requirement was created in a Jira project, the functionality automatically adds all project developers as watchers. As a result, the development team is immediately informed of the new requirements, enabling better coordination and timely implementation. | |
| Notify the support team about internally found bugs / problems |
|
Add or remove watchers |
When an issue is identified as a bug, the functionality automatically adds all members of the support group as watchers. This ensures the support team is promptly informed about the bug, enabling them to communicate effectively with customers regarding any errors that occur on the customer side.
|
|
| Notifying the parent issue watchers about new sub-tasks |
|
Add or remove watchers | Once a sub-task is created, the functionality automatically adds all watchers of the parent issue as watchers to the sub-task. In this way, it becomes possible to ensure that the watchers of the parent issue remain informed of new developments and updates at the sub-task level and maintain a comprehensive overview. | |
| Providing information to the onboarding team about new issues created by team members |
|
Add or remove watchers | Each time a team member creates a new issue, the "Add or remove watchers" functionality automatically adds all colleagues from the onboarding team as watchers. This feature immediately informs the entire onboarding team about new issues, improving team coordination and support. |