Display all known BUGS and their status online for ESRI users to view

[DataOfficer]

There have been multiple occasions where I have come across issues in ArcGIS Pro and other ESRI products and searched for relevant documentation or solutions, but with no useful results. After subsequently posting in the Community or contacting Technical Support, these are sometimes known BUGS, with no public information on them. Valuable time is repeatedly wasted by users searching for issues they come across that are known to be BUGS by ESRI, but with no or limited information publicly available - leaving users in the dark. Similarly the time of ESRI staff in the Community and via Technical Support must regularly get wasted responding to the same issues being raised. 

I propose that it would be useful for users and ESRI staff alike to make details of all BUGS available publicly to ESRI product users so that less time is wasted searching for error solutions. updates or information.

As an example, today I came across an issue with Select Layer By Attributes in ModelBuilder when using Scheduled Tasks. This is a known BUG (BUG-000131693), but with no public information about it. Only by posting in the community and getting a response from an ESRI staff member was it possible to get some information. It would have been much easier if googling the issue came up with the BUG details.

[JohnSobetzer]

This help?

https://support.esri.com/en/Search-Results#search?q=bug%20list&content-type=Technical%20Articles

[KoryKramer]

Hi @DataOfficer sorry that you encountered a bug. It is possible to search on support.esri.com when you feel you may be encountering a bug:

https://support.esri.com/en/Search-Results#search?q=Select%20Layer%20By%20Attributes%20error&content...

Filter by content type:

[DataOfficer]

Hi both,

Thank you for the quick responses and directing me to that resource. I was not aware of this. I must have been searching the wrong part of the ESRI website.

Are these indexed and searchable via search engines also? They don't seem to appear in Google searches.

[Anonymous User]

Reopened here with specific enhancements in mind.

[DataOfficer]

Just to add as well that support.esri.com does not appear to display all known bugs (e.g. BUG-000145126).

[JoshuaBixby]

@KoryKramer, "searching" is just one form of making information available.  I think what the OP is after is more than just searching, having the ability to browse too.  The shortcoming with searching is that it depends on the people who logged the bug and the people searching for the defect to have the same terminology, which often times isn't the case. 

[KoryKramer]

@DataOfficer it looks like that bug was incorrectly flagged as a bug in a beta version of the software. In general, bugs against beta versions are not published. There can be legitimate reasons to not make all bugs public (think security) but in general we try to make known issues public to help users self-serve through the Support site.

If you do find an issue on support.esri.com that is affecting you, I encourage you to use the Subscribe button which sets you up for notifications on that issue, but also importantly increments the count of affected users in our backend systems that development teams use to help prioritize issues.

We'll take into consideration the suggestions provided on this thread as well as the other to see if we can improve discoverability of known issues.

Cheers

[DataOfficer]

@KoryKramer thank you for the added detail. 

It would be very useful if the technical support knowledge base results came up using a search engine, similar to esri community posts.

[HollyTorpey_LSA]

@KoryKramer I can't find BUG-000150564 (Exporting PDF's from ArcGIS Pro 3.0 and combining them in Adobe causes them to turn blank). I read about it in this post and would like to know what the status is. Any tips on finding that information? Thanks in advance!

[KoryKramer]

Hi @HollyTorpey_LSA It just hasn't been published yet - it is probably in copy review.

Here is the status, though. We have a fix for it in the 3.1 codebase and are looking to get it included in the first patch for Pro 3.0. That is targeted for mid-August. I can't give any guarantee at this point in time, but that is the plan. I apologize for the inconvenience on this one, but hopefully knowing the status on a fix is helpful.

Cheers