Bug Tracker Issues

[TheRealMC]

Hi all,

This morning I noticed that I cannot see any of my submitted or voted-on support tickets in the Bug Tracker:

     Issues Created: 0

     You haven't created any issues

     Issues Voted: 0

     You haven't voted for any issues

Looking in the browser console, it looks like a 500 error is getting returned for both the created and voted API calls:

HTTP Status 500 - Request processing failed; nested exception is org.springframework.web.client.RestClientException: Could not extract response: no suitable HttpMessageConverter found for response type [class com.adobe.jira.model.v2.SearchResult] and content type [text/plain]

Additionally, the following 500 response is returned from the search API call:

HTTP Status 500 - Request processing failed; nested exception is org.springframework.web.client.HttpServerErrorException: 503 Service Unavailable

I've tried on multiple computers on various networks, each with the same result. Anyone else experiencing this?

Best regards,

Mike.

[Dave Watts]

I haven't used the bug tracker in ages, but they do have a FAQ which says:

"How do I report an issue with the Adobe Tracker site?

Please use the Add bug or New feature tab to let us know about issues that you are facing with the Tracker application or feature enhancements that you would like to see. Please select the Product as “Adobe Tracker” and Version as “1.0” when submitting your bugs and/or features."

Sadly, I don't think Adobe has a way to manually report issues with the tracker. So, I recommend you send an email to cfsup@adobe.com.

[TheRealMC]

Thanks for the suggestions, Dave.

The Add Bug form doesn't work (didn't expect it to, TBH), because dynamically filled dropdowns are failing to get populated due to the same 500 responses.

I'd already emailed cfsup, hoping to get some information back from them.

Best regards,

Mike.

[Charlie Arehart]

You're not alone, Mike. I've experienced the past couple of days, and on and off over recent weeks. Glad to hear you emailed them. Let's hope they address it.

BTW, I tweaked tour original post to turn your reference into a link--for those who may not know the url or just to make it easier for folks just to click on it. 🙂 To be clear, I very rarely edit folks' posts. In this case I hoped you'd have no reason to object to the slight tweak, and I didn't want to leave you wondering about the change. 🙂 

[TheRealMC]

In this case I hoped you'd have no reason to object to the slight tweak, and I didn't want to leave you wondering about the change. 🙂 

No problem at all, Charlie!  🙂 

[TheRealMC · Accepted solution]

CF Support opened a support case to look into it, and confirmed that the immediate issue was resolved. I asked if the root cause had been found, so as to stop it happening sporadically, and was told that the development team is investigating.

Best regards,

Mike.

[Charlie Arehart]

Thanks for the update--and for pressing the point with them.

Would be nice if they'd setup some periodic monitor, to check. Beyond any logged in user not seeing their own bugs reported or ones they voted on, while the problem happened even visiting an existing bug reported it was not there. That's how they could easily monitor without need of a login (which can be more challenging).

[BKBK]

Hi all, thanks for raising the Bug Tracker issue with Adobe. I faced it too last week. 

Funnily enough, the Bug Tracker is where you report bugs about the Bug Tracker itself. That is clearly a design fault. 

Anyway, the present issue seems to have been resolved.