nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to setup default watchers for Components in JIRA?

Vishal Gautam

Is there a way to setup default watchers for specific components in JIRA? Something like Default CC of Bugzilla. There is a JIRA Components Watcher Plugin, but it's not yet supported for 6.0 and as per the author it may be sometime, so wondering if anyone has done this using some other way.

Basically, what we need is whenever an issue is created and some components are selected, all the default watchers of the component should automatically become watchers of this issue.

Accepted answers

unknown

The solution that works for us is the JIRA Component Watcher add-on.

https://marketplace.atlassian.com/plugins/com.burningcode.jira.plugin.jiracomponentwatcher

Notes:

1. This add-on is not available in JIRA OnDemand

2. The term "Watcher" is a bit of a misnomer with this add-on as it does NOT set the Watchers field associated with an issue. Rather it triggers a Notification Event when an issue is created in order to send an e-mail to the list of users, or groups, that are associated with a Component at the Project level.

All comments

Renjith Pillai

A simple method is to create a group email address and add it as a user in JIRA. Then use this user as the Component lead. Also add the component lead to the notification scheme.

So who ever is part of the group email address will receive the email whenever any change happens to issues with those components.

Vishal Gautam

We already have done this to achieve Deafult Assignee functionality, so a new bug gets assigned to a group of folks who are responsible for triaging and then assigning to appropriate engineer. Ideally we want to keep Default CC list separate, but I can see that by merging the 2 lists into one this can work as an alternative. Thanks for the reply!

Vishal Gautam

Actually this solution of merging the default assignee and default cc on components will not work for us, since for the 50-60 components we have there are only a handful of default assignee aliases, but a lot more default CC groups are needed. Ideal would be JIRA should allow us to assign a group as default watchers just like it allows us to set a Component lead.

This question is still open.

Anthony Monticc1

We also need the ability to assign a Group of Users to 'watch' a JIRA issue.

Has this been added ?

Thanks,

Tony

unknown

The solution that works for us is the JIRA Component Watcher add-on.

https://marketplace.atlassian.com/plugins/com.burningcode.jira.plugin.jiracomponentwatcher

Notes:

1. This add-on is not available in JIRA OnDemand

Moriah Chandler

I use JIRA Workflow Toolbox and have added a post-function to the Create Issue step on the workflow. Using "Set a Field as a Function of other Fields" and the settings shown in the screen shot works perfectly.

It doesn't have to based on issuetype (we only want to add the watchers on bugs) and could be based on virtually any condition. The %{00125} is the Component Lead and is added to all bugs if a component is selected. See https://bitbucket.org/fcarmario/jira-workflow-toolbox/wiki/Homefor more information.

Unfortunately, this addon is not available for on demand.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira