In my opinion, if you experience any unusual or unexpected behaviour in ArcGIS Pro, lodge a support case.
Here is why:
In another discussion, Esri staff mentioned that they have a bug list that is not public and that they rely on users lodging support cases to judge when/if these bugs are to be handled.
Quote:
"We do have an internal bug. Currently it is sitting in our backlog. I do not know when we will get to it. I'll make note of your query and perhaps it might be something we can bump up in priority.
Unfortunately, this internal bug cannot be tracked outside of Esri. If you want to keep track of this issue you should contact support and enter a bug with them. Entering an issue with support also helps us gage how many are being affected by a bug and helps us prioritize our work. Having a bug number generated from a customer such as yourself makes a real difference. "
This particular case revolves around weirdness in the pdf export options of a map series.
I have experienced the issue but thought it just quirky and have not lodged a case.
Now I hear from Esri staff that it is an internal known bug, but on the backburner until enough people complain lodge cases (with enough supporting info that the regional resellers are in a position to forward them on to Esri Inc).
From a technical & resourcing perspective I understand the process and the reason why these processes and cases exist.
From a small business perspective, paying a lot for licenses to give my clients the best results possible, I am frustrated as I know the local reseller will not pass on my issue to Esri Inc unless they can reliably replicate the issue.
I feel the time required for both myself and the local reseller to replicate, test, document, etc an already known issue is very inefficient and there has to be a better way.
Until we (Esri and clients) find a better way to track issues, all I can come up with is to just lodge any and all behaviour that is unexpected; at the least, it will help everyone that is subject to an unlisted bug that is sitting on a shelf waiting for attention.
If you read this while at UC please raise your concerns with the Esri people you intersect and give us "ROW, Dusty" people some feedback.
