Anyone else having issues with JIRA Autowatch? The name selector just spins for us now

[Nathan]

JIRA autowatch has been working well, so we haven't changed anything for a few weeks. It seems, possibly when the new JIRA was officially released, that it stopped working. Anyone else having this issue

Or, does ayone know how we can get Atlassian Labs to look into the bug? I'm trying to ask this question here in case this is the way to do it :)

[David Fischer]

This is indeed caused by a Jira Cloud regression, more specifically in the AP.request JavaScript API of the Connect Framework.

There is an easy workaround, but it requires a small code change to the add-on (we had the same issue on our add-on). Maybe if you raise a support request with Atlassian?

[Nathan]

Thanks David. Following that procedure it says you have three avenues of getting help - here on the Q&As, writing a review, or getting a partner to support the app. Not sure how a partner can update the code of this app, maybe it's open source? Any chance you / your team is able to do that if you have a good idea what needs updating on the AP.request JS API?

[David Fischer]

Cloud add-ons can only be maintained by the publisher of the add-on, because they're not just software, they're a service (SaaS).

You need to raise a support ticket with Atlassian (support.atlassian.com).

[Boris MBOUMEHANG]

Hi Nathan, 

If still needed, there is another version of that plugin, released by Mohami: Autowatch for Jira. It works pretty well with the same functionnalities (our team uses it), but it is not free. 

Thanks.
Boris