In the past months, I've submitted some new bug reports:
BUG-000175441 Clicking and dragging row headers in the attribute table to select multiple rows causes the table to scroll left.
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.
Hi @ChristianWells and @Bud
Our bug pages are searchable by Google and other search engines.
I think the issue that makes searching on Google inconsistent is that bugs are taken offline briefly for editing and then returned to the support site. After that we have to wait for Google to crawl through the support site again to update their search results.
The bugs are available through the support site search more quickly because our search tool indexes our own content more often than Google indexes our content.
We have tried to minimize the types of edits that cause bugs to be temporarily removed, but there still are some edits that trigger a copy review before they can be returned to the support site. We copy review the bugs so that no public field contains customer information or internal only information.
I don't think it is a matter of formatting the search query, using the bug id and "Esri" or "Esri support" should work fine.
BUG-000140702: Right-clicking and selecting paste does not work whe.. (esri.com) is fixed at least, the other two didn't show
Does anyone outside of the open source community maintain a bug database with public access?
I think IBM does. I don't remember ever dealing with a bug that wasn't posted publicly. If a bug was created from one of my tickets, then it would be posted online.
I'm sure companies have their reasons to not share their bugs with the public, I get it. But so much time could be saved if we had access to it. It's a waste of time for me to reach out to Esri support for something they are already aware of. Not to mention it's a waste of time for Esri support to spend time supporting end users when the bug has already been documented.
Agreed. I think Esri could save a lot of money by making it easier to find bug info. If I googled an issue and there was already a bug for it, then I'd subscribe to the bug updates rather than submitting an additional ticket.
The Esri business model is entirely built on having you contract with them for support so you keep paying.
If the software was easy to install and easy to use, the demand for support would shrink.
If the software was not buggy there would be less need to stay on a contract, you could just stick with a version for years.
Because their services are expensive it creates a substantial market for consultants too.
I don't feel I am being cynical, it is just the model they chose. But I do think if the software itself was the product and not support contracts, they would put less focus an annual new feature list and more on making things work better.
You're not wrong. This is exactly why there needs to be more competition in the GIS industry. Maybe companies would put more emphases on making a quality product instead of only fixing bugs in future versions, forcing you to pay for maintenance so you have access to future versions, which just introduces more bugs and thus starting the cycle all over again.
ESRI today... a name, a survivor from the seventies and eighties, which groans under the weight of its own semi-finished products, full of bugs! Of course, they know about it, but the fun is more complete with the users; it is more social, offers more Ideas, i.e. of well-paid user frustrations and...and justifies the existence of not only ESRI, but n similar ones. Business model or rot (???) Hmm...The first evolves legal responsibility/obligation! Rot just a fake story about respect, interaction with users and well-worn staleness.
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.
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.