Latest Contributions by ChristianWells

I'd like to respond to the idea that Esri deliberately removes bug entries from public view. I've discussed this in another thread, 'Why aren't more bugs reports shared publicly?' and want to reshare the information for awareness.  A bug won't display in the public view because it still needs to complete the internal review process of technical and copy editing. Any time we update a bug internally, this process starts over again to validate the new information, and the bug will have its publishing status changed, which in turn removes it from the public view.  The only other situation where a bug is not publicly shared is if it contains sensitive information, which is extremely rare.  ... View more

@AndrewMunn I wrote this doc when the old site was still around.  Can you provide an update and timeline of when the website will have this feature re-added? ... View more

@JoshuaWatson3 I'm looking into this with the web team and will get back to you.  In the meantime, here is a good starting point to search based on products and patches: https://support.esri.com/en-us/search?cardtype=patches+and+updates ... View more

I'm unsure why the 'Feedback' form doesn't show for you. I suggest trying in incognito or maximizing the window to see if it shows up. In the interim, I sent you a PM with an email address to give direct feedback to the team.  ... View more

Hi Bud, when viewing the new support website from the main pages such as Overview, do you see the' Feedback' option on the web page's right side (screenshot below)? You can leave feedback there even as it relates to the search features. If you don't see the feedback form, we can explore other options for getting your feedback to the team.   ... View more

@Bud, thank you for the reminder.  Digging into this, I found that any time a bug is modified or edited, including when a product team changes the fields for the latest version reproduced, the bug is taken offline immediately. Then it has to be republished by our copy editing team.  I acknowledge this is not a good experience, and the web team has it on their backlog to ensure bugs persist until they are explicitly republished.  ... View more

@Bud I appreciate your feedback on this. Are you asking to see more than just the synopsis/subject line and the details of the user story? ... View more

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.  ... View more

Current plans are March: https://www.esri.com/arcgis-blog/products/arcgis/announcements/coming-soon-new-technical-support-site-experience/ ... View more

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. ... View more

Thanks, Bud - I reached out to the web team on these as examples and waiting to hear back.  ... View more

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. ... View more

I want to offer some insight into the process of logging a bug which explains why some bugs aren't visible. Some of the information below may be common knowledge, and I want to leave this here in case others stumble upon this thread. Technical Support is the point of contact to validate and identify a defect.  We build a reproducible case with workflows, data, and software logs to verify a potential defect.  We also research our existing internal resources to see if a bug already exists and an accurate match. Once we log a new defect or identify an existing one, we attach it to your account, and it shows up in My Esri for Authorized Callers.  If you need Support access, you can request permissions through MyEsri by following these steps.  The defect then undergoes a two-step review process for technical accuracy and copy editing. Some defects may need additional testing and validation during the technical review process, extending the review process.  Once the defect passes through our copy-editing process, it makes its way to the Support website, where you can search for bugs using this link. Esri Support Search. (Make sure the filter is set to "Bugs"). As @DanPatterson pointed out, one of the bugs can be found on the Support website. The other bugs you listed are in our technical review process, which is why they can't be found on the Support site.  @Bud, if you have specific questions about any of the bugs you listed or want to discuss this further, please feel free to send me a private message, and I'll be happy to connect. ... View more