problems with copying watchers


With the update of 6.0.0 (at least I think that is what caused it) when a users clicks on clone watchers it clears the watcher field (usually populated with the above mentioned plugin). If that is not checked the watchers are copied across.

Hi Pat,

I am constantly getting this error message when trying to clone++ a ticket:

Error rendering 'issue-watchers-field'. Please contact your JIRA administrators.

If I check the "Copy Issue Watchers" box then the watchers disappear from the new ticket. If I leave it unchecked then they are copied successfully.
For reference, this is the latest ticket I opened:




Server Jira 7.3.1 also have the bug watcher notification plugin 3.1.8-JIRA7. In the past an error has come up about this plugin but things worked as expected.


Pat Noack
August 14, 2017, 10:54 PM

After removing all updated plugins on a test jira and then updating all of them on an older test jira I finally discovered that it was a modification to the Jeditor plugin settings that broke everything. I changed FOrce native links from Jeditor LInks to Native links and all my watcher based scripts broke.

Thank you for your help

Pat Noack
August 10, 2017, 5:19 PM

log file during the time that word file was created

Pat Noack
August 10, 2017, 4:12 PM

I had only put in org.swift.jira.
I have enabled the debugging and I will try to clone a few tickets to see if I can reproduce what users are complaining about.

Former user
August 10, 2017, 4:07 PM

You can go to Jira Administration --> Logging and profiling --> Configure

Then add an entry with org.swift.jira.cloneplus and in DEBUG mode.

This will configure the plugin in debug mode.

Pat Noack
August 10, 2017, 4:01 PM

I thought I had put cloneplus in DEBUG mode but I do not see any cloneplus-diag log. How do I put your app in debug mode in jira. I would be happy to send you log files. These errors were seen in the UI.

I do know that on some of my projects I have a post function that adds watchers to the tickets. This function stopped working when I updated plugins. I have also contacted the developer of the watchers plugin that I use to take a look at this.

Here is an example of a post function in one of the projects which used to populate the watcher field. This stopped working about the time that clone++ started having weird behaviour dealing with watchers.

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.Issue
import com.atlassian.jira.user.util.UserManager
import com.atlassian.jira.issue.watchers.WatcherManager

def watcherManager = ComponentAccessor.getWatcherManager()
def userManager = ComponentAccessor.getUserManager()
def users = ["harlee.c", "zhigao.yao", "n.hangzo", "zhigao.yao", "hongbin.wei", "rc.herrera", "kunal.shenoy", "chunxin.chu", "santosh.c", "r.reznikov", "wayne.l", "carlos.olle"] //user keys of users you want to start watching the issue
def project = issue.getProjectObject();
//log.warn ("project key:" + project.getKey())
users.each { userKey ->
def userToWatch = userManager.getUserByName(userKey)
if (userToWatch)
watcherManager.startWatching(userToWatch, issue)
log.warn ("User with key " + userKey + " is not a valid user")
Many projects have similar post-functions on create but none that I can find on any other transition.

Once I know how to get your module in debug mode I will send the logs



Aravind Kashyap




Support Entitlement




Affects versions