Customers have installed this app in at least 4,151 active instances.
    by Ray Barhamfor JIRA Server 7.0.0 - 7.4.3 and more versions
    Versions available for JIRA Server 3.11 - 6.2.7
    JIRA Server 6.3.1 - 6.4.14
    Ray Barham supports this app.

    Get support

    Data Center
    This app is compatible with the clustering and high-availability capabilities of our products.
    Get it nowFree app

    Watcher Custom Field

    Watcher Custom Field

    Update watchers on issue create/edit

    Search for watchers

    Use throughout JIRA

    Ability to add and edit watchers when creating and editing an issue.

    Can search for watchers from the issue navigator.

    Can be used in permission schemes, issue security schemes, workflows, etc.

    More details

    This plugin adds a custom field type that allows watchers to be modified on issue creation/modification. It interfaces with the existing watchers mechanism.

    Only users that have the "Manage Watcher List" permission have access to this field. If a user does not have permissions, they will only see the message "You do not have permission to manage the watcher list." with a list of the current watchers.

    Can be used to search for watchers or anywhere else a custom user field can be used (issue security, project roles, permissions/notification scheme, etc).

    User reviews

    Sign in to write a review
    by Bernd W Neumann on 2017-07-11
    Hi! Who can be a watcher? Anyone? Or does (s)he have to be a member of a certain group? Kind regards Bernd
    Was this review helpful?YesNo
    Ray Barham

    Hi Bernd,

    It's dependent on project permissions. The concept of "watcher" is built into JIRA and my plugin interfaces with that functionality. For more information on JIRA watchers, checkout the Watching and Voting on an Issue guide.

    Kind Regards,


    by ChungKyu Lee on 2017-04-28
    When I press enter key in watcher filed, the full name change to user name. I want to not change like reporter field. How can I solve? Thank you.
    Was this review helpful?YesNo
    Ray Barham


    Well, if I'm understanding you correctly, the only way to change it would be to change it for all fields that use the multi-user velocity template. The plugin uses this default template. I believe the file is "atlassian-jira/WEB-INF/classes/templates/plugins/fields/edit/edit-multiuser.vm". For more info on templates, see JIRA templates and JSPs page. Good luck. Feel free to send me an email if you have any further questions.


    by Sven Wenzel on 2017-01-10
    I have a problem if I cloning an issue. The watchers stay in the cloning issue.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    Ray Barham

    Hi Sven, sorry to hear you're having problems. Can you elaborate?

    Are you expecting watchers to not be cloned? If so, this is a byproduct of using a custom field. By default in JIRA, watchers are not cloned. The custom field adds that ability. I can look into making that configurable, though.

    Are you not able to remove watchers from cloned issues? If not, consider updating to the latest version of the plugin. There was a mechanism introduced in JIRA 7 that caused this to happen but has been fixed in the latest release.

    Also, if you have any other problems, feel free to create a ticket on the plugins homepage, https://bitbucket.org/rbarham/jira-watcher-field-plugin.

    by Bulanov Maxim on 2016-09-27
    Thanks you Ray! This is great plugin! Could you add issue number to Sub-Tasks list?
    Was this review helpful?YesNo
    Ray Barham

    Hey Bulanov,

    I'm glad you're liking my plugin! Thanks for using it.

    To answer your question, I don't see why not. You would probably need to edit a velocity template to do it, though. Actually, now that I think about it, I believe I did just that about 6 years back when I was a JIRA admin. Can't remember what I did, unfortunately.

    by Chander on 2016-09-06
    Hey Ray, I see that the plugin version compatible are from JIRA 7.0.0 to 7.1.9 and 7.1.0 to 7.2.1. Can we expect Compatible release of this plugin supporting 7.0.0 through 7.2.1 ? If we would like to Upgrade JIRA from 7.0.10 to 7.2.1
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    Ray Barham

    Hey Chander,

    Sorry for just now responding. I didn't notice your review until now. Actually, yea, they are compatible. I just did a quick test to make sure. I must of selected the wrong dropdown when updating the plugin. I've fixed the issue. Thanks for bringing it to my attention.


    Ray Barham provides support for this app.

    Vendor support resources


    Find out how this app works.


    Collaborative documentation platform hosted by this vendor.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.


    Version 2.6.10 JIRA Server 7.0.0 - 7.4.3 Released 2017-05-17


    Bug fixes and configuration enhancements


    * Issue 44: Added watcher event listener that updates the watcher counter for an issue if it is out of sync.

    * Issue #55: Fixed issue with renamed users not returning results in search for watcher field. Refactored some code. Fixed some of the broken/disabled tests.

    * Adding settings for ignoring and automatically removing disabled users.

    * Updated plugin version to 2.6.10


    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Watcher Custom Field for JIRA via search. Results include app versions compatible with your JIRA instance.
    5. Click Install to download and install your app.
    6. You're all set! Click Close in the Installed and ready to go dialog.

    To find older Watcher Custom Field for JIRA versions compatible with your instance, you can look through our version history page.

    Similar apps