Jira Server 6.3.1 - 7.11.2
Watcher Custom Field
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).
Reviews for cloud
(55)Sign in to write a review
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,
-Ray
Hello,
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.
-Ray
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.
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.
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.
Reviews for server
(55)Sign in to write a review
Hi Anas,
Thank you for the great review! I really appreciate it.
The plugin is indeed compatible with Jira 7.6.2. Plugin version 2.6.16 should work with Jira version 7.0 -> 7.11. The marketplace should allow you to install the correct and latest version of the plugin for your Jira instance.
Feel free to put in a ticket in my issue tracker if you have any problems.
Kind regards,
-Ray
Hi Vladimir,
Sorry for just now responding after so long. Thank you so much for the great rating!
As for using the standard Jira functionality, I'm afraid there isn't much I can do about it. There really isn't a way that I'm aware of to have Jira set a notification when using the standard Jira functionality. It "might" be possible to use a event listener, however, that would cause a conflict or duplicate notifications or something with the custom Watchers field.
Again, thank you again for the great review and sorry for just now responding.
Kind regards,
-Ray
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,
-Ray
Hello,
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.
-Ray
Reviews for Data Center
(55)Sign in to write a reviewHi 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,
-Ray
Hello,
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.
-Ray
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.
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.
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.
Cloud Pricing
Server Pricing
Data Center Pricing
Ray Barham provides support for this app.
Vendor support resources
Find out how this app works.
Collaborative documentation platform hosted by this vendor.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 2.7.1 • Jira Server 7.12.0 - 8.2.4 • Released 2019-01-08
Summary
Fix issue moving tasks
Details
Issue #79: Fixed issue where moving a task would cause an exception `com.atlassian.jira.issue.customfields.impl.FieldValidationException: User 'null' was not found in the system.` exception to be thrown in the second screen
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Watcher Custom Field for Jira via search. Results include app versions compatible with your Jira instance.
- Click Install to download and install your app.
- 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
