You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I searched, if answer is there I missed it. I followed the tag for the plugin, it the answer is there I missed it.
Is there an alternative to burningcode's now defunct Jira Watcher Custom Field plugin?
So I haven't a clue how this plugin works, can someone explain to me how I would check if it's even being used or setup in Jira? Assume I know nothing of Jira, but I do know Linux/Postgres/Apache, etc. So even though I have it enabled, it's not clear if it's actually in use.
Otherwise I guess I'll clone to a test instance, disable it and see what breaks, but I haven't a clue how to test it.
Or what to replace it with if it does break and my users say they need it.
We just upgraded our test environment from 8.20.1 (still works) to 8.22.2, and it is broken.
Those were the ones I noticed, but it's more than enough to stop us from upgrading production. We rely heavily on watchers and the similarly failing Jira Component Watchers app, and now we are stuck.
I will not that if I disable the two apps I can still add/remove watchers from existing issues, but I cannot add them to new issues.
We migrated from 7.0.1 to 9.1.x and this plugin was very useful, I couldn't contact the developer and we don't see it available anymore.
I have tried to decompile it and fix the error, but with no luck.
I see that someone can fix it, could you please share it?
Or send it by mail? or a Drive?
Thank you so much.
@K M Would you mind sharing your patch? I've been keeping a clone of the original source here but unfortunately it's a pretty old version (not 2.8.5)
My story: I didn't want to setup the whole plugin development environment. I attempted a decompile and added "ComponentAccessor.getComponent(FeatureManager.class)" to WatcherFieldType.java
genericConfigManager, multiUserConverter, applicationProperties, authenticationContext,
searchService, fieldVisibilityManager, jiraBaseUrls, userBeanFactory, groupManager,
projectRoleManager, soyTemplateRendererProvider, userFilterManager,
Threw that file into "external-src" and ran ant to compile (also had to throw a few files into the /lib sub-folder")
Was getting NoClassFoundExceptions so had to hack the manifest.MF file with: com.atlassian.jira.config;resolution:=optional
Re-packaged it all up and it's "working" I guess in Jira 9.3.0
Can I have a copy of fixed version of Component watcher and water field, too?
we upgraded to 9.3 and have same issue.
still have below errors during re-index after uninstall those 2 add-ons.
Caused by: io.atlassian.util.concurrent.LazyReference$InitializationException: io.atlassian.util.concurrent.LazyReference$InitializationException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.burningcode.jira.issue.customfields.impl.WatcherFieldType': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.burningcode.jira.issue.customfields.impl.WatcherFieldType]: Constructor threw exception; nested exception is java.lang.NoSuchMethodError: 'void com.atlassian.jira.issue.customfields.impl.MultiUserCFType.<init>
thanks in advance,
Hi Deigo, I see what you mean, the configuration menu is erroring out with a 405 method not allowed error.
After some research, this is due to changes in Jira 9, in particular Verification of Jira web action request methods
I've added the necessary annotations to the WatcherFieldSettings.class and recompiled:
Unfortunately, it's still giving out a 405 error and I'm stumped. It works if you add the DarkSiteFlag feature but that is not recommended
Maybe someone else more knowledgeable can answer/help. For now, I'll pull the download link offline.
Update: I fixed the problem and uploaded 22.214.171.124 for testing.
It seems to me that I am in error, I was looking for the "Jira Component Whatchers" and you are trying to repair the "Field Whatchers".
They are two different plugins and I think both stopped working after the migration to Jira 9.x.
Exactly, I was testing it and I realized the error, that's why when I went to see the components the access didn't appear in the menu.
Sorry for me error.
Anybody can help with that issue?
I'm at version jira server 8.20.4. Need upgrade it until latest version. But no success with JIRA Watchers field and Watchers Component, Alo I use Security level that has custom watchiers field.
How is possible to upgrade jira server from 8.20.4 till latest version and watchers field and component watchers able to work?
could somebody share the the "fix" OR the give a steps to do it ourself?
thank you in advance.
Hi, if anyone is still looking I have an App called Watch It that allows you to watch components in a project and to add watchers during issue creation. It is available on Jira server, data center and cloud.
You can check it out at: https://marketplace.atlassian.com/apps/1213851/watch-it-for-jira
This is a post-function scriptrunner script that works if you have a static user to add as a watcher. Place script after the "Creates the issue originally" post function on the create transition.
watcherManager = ComponentAccessor.getWatcherManager()
userManager = ComponentAccessor.getUserManager()
user = userManager.getUserByName(
This would be the ideal solution except for cases where Issue Security Levels is being used with watchers. In that case, you'd want watchers to sync with that field when changes are made. I guess there would need to be a global Script Listener that updates the user field with changes to watchers.