Ok, then there's two more things to do 1) A 500 error actually implies that your application is trying to hit an invalid url in JIRA. But as it's churning for ages, it suggests it's a url that JIRA is trying to process and eventually saying "no" to. That's why I suggested that JIRA might be logging the problem. You'll need to contact Atlassian support to get that information from your system 2) As the url looks wrong or unresponsive, I'd look at the config and logs in Heroku - it's trying to do something invalid and might be logging why.
Hi Nic, I'm getting no error readouts in JIRA, it just spins perpetually because the PUT request (made to https://autowatch.herokuapp.com/autoWatchRule/beaucoup.jira.com/1588) comes back with a generic 500. When viewing the response on updating these autowatch rules on a project, I see that it comes back with:
<h1>Oops, an error occured</h1>
This exception has been logged with id <strong>6oa7lik7n</strong>.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot