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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?
I'm in the same boat, and wondering the same thing. It's been working with version 8.5.x for a while, but I need to upgrade to 8.13.10 now.
Ken, are you running Jira v8.13.x and is the plugin still working for you there?
We bit the bullet and upgraded anyway, and it's working. At least as far as I can tell.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When we upgraded to 8.13 in 2021Q1, it was still on the supported list. I would have noticed otherwise. I just discovered it was dropped 10 minutes ago when I was trying to find a link to docs for a user!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Blech. I just upgraded to 8.13.13 this morning... didn't notice anything. I suspect it will have to be disabled for the next big upgrade process.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for providing that info on 8.21.1, Darren. We'll be going to 8.20.5 (LTS) shortly and will watch to see if this breaks in that release as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How bad is the breakage? I guess we will be moving to something newer when we get a chance, but honestly, this is a slowly dying instance so it might just move to the cloud at some point. Maybe. I just admin the system, not the Jira info itself.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
Fun......
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@John StoffelIt adds a custom field. You should be able to go to Administration > Custom fields and find the field by type. If you find some, you can track back via their screens to project etc. and find where they are used.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the hints. Looking at my setup, it looks like the darn thing isn't even used. Heh. And nothing has broken according to my users in the test instance I setup for them which was a clone of production.
I apprecaite all the help people have given me here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The plugin broke after upgrading to 8.22.2 as well and now I am not really sure if there is any replacement for it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We just upgraded our test environment from 8.20.1 (still works) to 8.22.2, and it is broken.
Effects:
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I somehow managed to fix the plugins by decompiling them and fixing the broken constructor. The actual issue has been already reported - https://jira.atlassian.com/browse/JRASERVER-73747
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @K M ,
could you share the "fixed version you created" OR the steps to do it ourself?
thank you in advance.
Kind regards,
Matt
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh.. I only fixed versions 2.8.3 and 2.8.5. Not sure how compatible they are with 2.8.1
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I will try to send it to you later this week - if I don't (I will be at a conference) please remind me about it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for that, I see the app itself not available anymore on the Marketplace...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, unfortunately I couldn't find anything, neither bitbucket repository nor the addon on marketplace.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Matt Van Kuyk
Hi Matt, how can I contact you? Would you mind sharing the fixed version of Jira Watcher Field with me too?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Matt Van Kuyk @K M Hi, would you mind sharing the fixed version of Jira Watcher Field v. 2.8.5 with me plaese? artemspecspec@gmail.com
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Matt Van Kuyk I think your email must be being removed by a bot or something.
Is there any chance you could post some instructions on how to do this for us please.
Many thanks
James
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can anyone figure this out? Maybe Atlassian knows how to get past this issue?
Would really appreciate a solution to this...
Regards,
Matis
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi everyone,
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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
import com.atlassian.jira.config.FeatureManager;
.
.
.
super(customFieldValuePersister,
genericConfigManager, multiUserConverter, applicationProperties, authenticationContext,
searchService, fieldVisibilityManager, jiraBaseUrls, userBeanFactory, groupManager,
projectRoleManager, soyTemplateRendererProvider, userFilterManager,
fieldConfigSchemeManager, projectManager,
ComponentAccessor.getComponent(FeatureManager.class));
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
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,
Sonya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Matt Van Kuyk
following this thread as we're also stuck at 8.20.x version as we use the Watcher field plugin; would also be interested to get your fixed version for testing, if possible.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Gaël NEUEZ , @Matt Van Kuyk , @Sonya S_ , @David Yu , @K M colegues, anybody is successful with jira watchers filed and component watchers in latest jira server version?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, following thread comments, I understand that @K M managed to create a fixed version, it would be great if we could get access to jar or source code...
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi David, thank you.
but I did test and it not working yet.
the error messages is:
The requested method GET is not allowed for this URL.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi David,
It was what I did, download the update and install it before trying it.
The installation works and raises the instance well. But when trying it gives the error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
@SupportedMethods({RequestMethod.GET, RequestMethod.POST})
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
jira.webactions.request.method.recognition.disabled
Maybe someone else more knowledgeable can answer/help. For now, I'll pull the download link offline.
Update: I fixed the problem and uploaded 2.8.5.2 for testing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi David, thank y for you time and dedication.
where you put the link for test?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi David,
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ahhh, Component Watchers. Maybe if time permits, I will also patch that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I patched Component Watchers. You can examine the commits to see the patches. Use/test at your own risk, no support given, yada yada yada. 🎅
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could you please share with us fixed version of "Jira Watcher Field" compatible with v8.22.x ?
Unfortunately, this add-on is causing chaos in our upgraded test instance.
Regards,
Sami S.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@David Yu Thanks for the response,
We are currently using Jira Server v8.22.6 & Jira Watcher Field v2.8.5
Regards,
Sami S.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the patched file, I uninstall and re-install with the patched file, got the following error
Regards,
Sami S.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sami, not sure what the problem could be. I tested locally on new 8.22.6 install and it worked for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Let me try by clearing the cache from the Plugin folders and will share the results.
Regards,
Sami S.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same error even after clearing the plugin cache. Any other solution you could recommend us?
Regards,
Sami S.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
Regards
Paul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
additional question, does anyone knows where "Component watcher" stored in database?
appreciate,
Sonya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
import
com.atlassian.jira.component.ComponentAccessor
import
com.atlassian.jira.issue.watchers.WatcherManager
import
com.atlassian.jira.user.ApplicationUser
import
com.atlassian.jira.user.util.UserManager
def
watcherManager = ComponentAccessor.getWatcherManager()
def
userManager = ComponentAccessor.getUserManager()
def
user = userManager.getUserByName(
"ComplianceSolutions@covius.com"
)
as
ApplicationUser
log.info(
"User"
+user.toString())
log.info
"Issue"
+issue.toString()
watcherManager.startWatching(user, issue)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It wont magically start working on newer versions, the changes were made by Atlassian development team and it's very unlikely they are going to revert to an old constructor.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Matis,
If I understand correctly, you say that the version
is jiracomponentwatcher 2.4 working fine on Jira Sever 9.1?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is it possible to get the fixed version 2.8.5 as 2.8.6 over Atlassian Universal Plugin Manager?
When not, please send me also the fixed 2.8.5.
Regards Harald
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We moved to 8.20.6 (LTS) and it did not break there. Looking at all the other comments, it appears to first break on 8:21.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.