In the past months, I've submitted some new bug reports:
When I google those bug report numbers, I don't get many hits.
Question: Why aren't those kinds of bug reports publicly available?
Thanks.
Solved! Go to Solution.
@ChristianWells , you seem to understand the support and defect processes well, so maybe you can have some influence on the following. It would be great if the URLs for bugs and defects were decipherable from knowing the bug or defect. For example, BUG-000094271 has a URL of support.esri.com/en/bugs/nimbus/QlVHLTAwMDA5NDI3MQ== . Whatever the rhyme or reason is behind turning "BUG-000094271" into "QlVHLTAwMDA5NDI3MQ==" isn't documented anywhere. For an organization with tens of thousands of GIS users that logs 50-100 defects and enhancements a year, linking internal documentation to Esri Support documentation is a very manual process. It would be nice if one could determine the URL by knowing the BUG or ENH number.
Update: For My Esri, both the old/classic UI and the new UI support URLs that are derived directly from bug or enhancement numbers. For BUG-000094271 and the My Esri classic UI, the URL is: my.esri.com/classic/#/support/bugs/BUG-000094271
Thanks, @JoshuaBixby - this feedback is helpful, and I will share it with our web team for the support website. I'm glad to hear it's consistent for My Esri.
@JoshuaBixby, like you mentioned, the bug numbers are in the URLs now. Nice!
support.esri.com/en-us/bug/the-attribute-table-of-a-joined-layer-in-a-mobile-geoda-bug-000155819
Why are some bugs googleable, like this one: BUG-000085841
But other bugs aren't googleable, like this one: BUG-000140702 ?
While that bug does have a permalink in the Esri Support Search site, I don't get any hits if I google the bug number or bug title.
Thanks, Bud - I reached out to the web team on these as examples and waiting to hear back.
I heard back this morning, @Bud - it sounds like they are already aware of the issue, and it's related to bugs going through the review and edit process multiple times. However, it is on their roadmap as they migrate the site to a new platform later this year.
In addition, @JoshuaBixby asked about the URL with the bug number instead of a GUID. This URL change is also planned for the new site migration and will help with SEO indexing.
Timelines can change, but this is being tracked, and I want to close the loop with both of you.
Christian, thanks for the updates. Here's hoping "later this year" is more like summer than 12/31/2022. 🙂
Here's an example of a bug I reported 9 months ago, but it still isn't available on the Esri Technical Support website: https://support.esri.com/en/search-results#search?q=000150273&content-type=Bugs
BUG-000150273 - ST_Geometry functions applied to the Shape field in Select By Attributes return the error message, "Error 000358: Invalid expression" if the feature class is registered as traditional versioned.
Reported: June 24, 2022
I'm told the bug is still "In Review". Does it normally take that long for Esri to review bugs?
I'm told the bug is still "In Review". Does it normally take that long for Esri to review bugs?
No. I looked at this on our internal system - this bug was reviewed in July 2022 and marked as published around the same time. I will reach out to the web team for troubleshooting.